Mobile communication system, source base station, target base station and user equipment

ABSTRACT

Provided is a communication system that can be normally and efficiently operated in the case where existing carriers and new carrier types coexist. A base station device and a communication terminal device are configured to perform communication in cells of legacy carriers LC1 to LC3 being existing carriers. When the base station device starts operating new carrier types NCT1 and NCT2, the NCT1 and NCT2 are associated with legacy carriers belonging to the same frequency band. For example, the NCT2 is associated with the LC2 or the LC3 and is not associated with the LC1. The legacy carriers LC1 to LC3 associated with the NCT1 and the NCT2 notify the communication terminal device of the information on the NCT1 and NCT2. This allows the communication terminal device to communicate with the NCT1 and the NCT2.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of priorityfrom U.S. patent application Ser. No. 16/597,621, filed Oct. 9, 2019,which is a continuation of and claims the benefit of priority from U.S.patent application Ser. No. 15/628,976, filed Jun. 21, 2017, now U.S.Pat. No. 10,512,085, herein incorporated by reference, which is acontinuation of U.S. Pat. No. 9,713,148, issued Jul. 18, 2017, whichclaims the benefit of prior International Application No.PCT/JP13/070983, filed Aug. 2, 2013, which is based upon and claims thebenefit of priority from Japanese Patent Application No. 2012-171871,filed Aug. 2, 2012; the entire contents of which are incorporated hereinby reference.

TECHNICAL FIELD

The present invention relates to a communication system including a basestation device and a communication terminal device capable of radiocommunication with the base station device.

BACKGROUND ART

Commercial service of a wideband code division multiple access (W-CDMA)system among so-called third-generation communication systems has beenoffered in Japan since 2001. In addition, high speed downlink packetaccess (HSDPA) service for achieving higher-speed data transmissionusing a downlink has been offered by adding a channel for packettransmission (high speed-downlink shared channel (HS-DSCH)) to thedownlink (dedicated data channel, dedicated control channel). Further,in order to increase the speed of data transmission in an uplinkdirection, service of a high speed uplink packet access (HSUPA) systemhas been offered. W-CDMA is a communication system defined by the 3rdgeneration partnership project (3GPP) that is the standard organizationregarding the mobile communication system, where the specifications ofRelease 10 version are produced.

Further, 3GPP is studying new communication systems referred to as longterm evolution (LTE) regarding radio areas and system architectureevolution (SAE) regarding the overall system configuration including acore network and a radio access network (hereinafter, collectivelyreferred to as network as well) as communication systems independent ofW-CDMA. This communication system is also referred to as 3.9 generation(3.9 G) system.

In the LTE, an access scheme, a radio channel configuration, and aprotocol are totally different from those of the W-CDMA (HSDPA/HSUPA).For example, as to the access scheme, code division multiple access isused in the W-CDMA, whereas in the LTE, orthogonal frequency divisionmultiplexing (OFDM) is used in a downlink direction and single carrierfrequency division multiple access (SC-FDMA) is used in an uplinkdirection. In addition, the bandwidth is 5 MHz in the W-CDMA, while inthe LTE, the bandwidth can be selected from 1.4 MHz, 3 MHz, 5 MHz, 10MHz, 15 MHz, and 20 MHz per base station. Further, differently from theW-CDMA, circuit switching is not provided but a packet communicationsystem is only provided in the LTE.

In the LTE, a communication system is configured with a new core networkdifferent from the general packet radio service (GPRS) being the corenetwork of the W-CDMA, and thus, the radio access network of the LTE isdefined as a radio access network independent of the W-CDMA network.

Therefore, for differentiation from the W-CDMA communication system, acore network and a radio access network are referred to as an evolvedpacket core (EPC) and an evolved universal terrestrial radio accessnetwork (E-UTRAN), respectively, in the LTE communication system. Alsoin the radio access network, the base station that communicates with amobile terminal (a user equipment (UE)) being a communication terminaldevice is referred to as an E-UTRAN NodeB (eNB). The EPC functions as aradio network controller that exchanges control data and user data witha plurality of base stations. The EPC is also referred to as an accessgateway (aGW). The system formed of the EPC and E-UTRAN is referred toas an evolved packet system (EPS).

Unicast service and evolved multimedia broadcast multicast service(E-MBMS service) are provided in this LTE communication system. TheE-MBMS service is broadcast multimedia service. The E-MBMS service ismerely referred to as MBMS in some cases. Bulk broadcast contents suchas news, weather forecast, and mobile broadcast are transmitted to aplurality of user equipments in the E-MBMS service. This is alsoreferred to as point to multipoint service.

Non-Patent Document 1 (Chapter 4) describes the current decisions by3GPP regarding an overall architecture in the LTE system. The overallarchitecture will be described with reference to FIG. 1. FIG. 1 is adiagram illustrating the configuration of the LTE communication system.With reference to FIG. 1, the E-UTRAN is composed of one or a pluralityof base stations 102, provided that a control protocol for a userequipment 101 such as a radio resource control (RRC), and user planessuch as a packet data convergence protocol (PDCP), radio link control(RLC), medium access control (MAC) and physical layer (PHY) areterminated in the base station 102.

The base stations 102 perform scheduling and transmission of a pagingsignal (also referred to as paging messages) notified from a mobilitymanagement entity (MME) 103. The base stations 102 are connected to eachother by means of an X2 interface. In addition, the base stations 102are connected to an evolved packet core (EPC) by means of an S1interface. More specifically, the base station 102 is connected to themobility management entity (MME) 103 by means of an S1_MME interface andconnected to a serving gateway (S-GW) 104 by means of an S1_U interface.

The MME 103 distributes the paging signal to a plurality of or a singlebase station 102. In addition, the MME 103 performs mobility control ofan idle state. When the user equipment is in the idle state and anactive state, the MME 103 manages a list of tracking areas.

The S-GW 104 transmits/receives user data to/from one or a plurality ofbase stations 102. The S-GW 104 serves as a local mobility anchor pointin handover between base stations. Moreover, a PDN gateway (P-GW) isprovided in the EPC. The P-GW performs per-user packet filtering andUE-ID address allocation.

The control protocol RRC between the user equipment 101 and the basestation 102 performs broadcast, paging, RRC connection management, andthe like. The states of the base station and the user equipment in RRCare classified into RRC_IDLE and RRC_CONNECTED. In RRC_IDLE, public landmobile network (PLMN) selection, system information (SI) broadcast,paging, cell re-selection, mobility, and the like are performed. InRRC_CONNECTED, the user equipment has RRC connection and is capable oftransmitting/receiving data to/from a network. In RRC_CONNECTED, forexample, handover (HO) and measurement of a neighbour cell areperformed.

The decisions by 3GPP regarding the frame configuration in the LTEsystem described in Non-Patent Document 1 (Chapter 5) will be describedwith reference to FIG. 2. FIG. 2 is a diagram illustrating theconfiguration of a radio frame used in the LTE communication system.With reference to FIG. 2, one radio frame is 10 ms. The radio frame isdivided into ten equally sized subframes. The subframe is divided intotwo equally sized slots. The first and sixth subframes contain adownlink synchronization signal (SS) per each radio frame. Thesynchronization signals are classified into a primary synchronizationsignal (P-SS) and a secondary synchronization signal (S-SS).

Multiplexing of channels for multimedia broadcast multicast servicesingle frequency network (MBSFN) and for non-MBSFN is performed on aper-subframe basis. MBSFN transmission is the simulcast transmissiontechnique realized by simultaneous transmission of the same waveformsfrom a plurality of cells. The MBSFN transmission from a plurality ofcells in the MBSFN area is seen as a single transmission by a userequipment. The MBSFN is a network that supports such MBSFN transmission.Hereinafter, a subframe for MBSFN transmission is referred to as MBSFNsubframe.

Non-Patent Document 2 describes a signaling example when MBSFN subframesare allocated. FIG. 3 is a diagram illustrating the configuration of theMBSFN frame. As shown in FIG. 3, the radio frames including the MBSFNsubframes are allocated per radio frame allocation period. The MBSFNsubframe is a subframe allocated for the MBSFN in a radio frame definedby the allocation period and the allocation offset (radio frameallocation offset), and serves to transmit multimedia data. The radioframe satisfying Equation (1) below is a radio frame including the MBSFNsubframes.

SFN mod radioFrameAllocationPeriod=radioFrameAllocationOffset  (1)

The MBSFN subframe is allocated with six bits. The leftmost bit in FIG.3 defines the MBSFN allocation for the second subframe (#1). The secondbit, third bit, fourth bit, fifth bit, and sixth-bit from the leftdefine the MBSFN allocation for the third subframe (#2), fourth subframe(#3), seventh subframe (#6), eighth subframe (#7), and ninth subframe(#8), respectively. The case where the bit indicates “one” representsthat the corresponding subframe is allocated for the MBSFN.

Non-Patent Document 1 (Chapter 5) describes the decisions by 3GPPregarding the channel configuration in the LTE system. It is assumedthat the same channel configuration is used in a closed subscriber group(CSG) cell as that of a non-CSG cell. Physical channels are describedwith reference to FIG. 4. FIG. 4 is a diagram illustrating physicalchannels used in the LTE communication system.

With reference to FIG. 4, a physical broadcast channel (PBCH) 401 is achannel for downlink transmission from the base station 102 to the userequipment 101. A BCH transport block is mapped to four subframes withina 40 ms interval. There is no explicit signaling indicating 40 mstiming.

A physical control format indicator channel (PCFICH) 402 is a channelfor downlink transmission from the base station 102 to the userequipment 101. The PCFICH notifies the number of OFDM symbols used forPDCCHs from the base station 102 to the user equipment 101. The PCFICHis transmitted in each subframe.

A physical downlink control channel (PDCCH) 403 is a channel fordownlink transmission from the base station 102 to the user equipment101. The PDCCH notifies the resource allocation information for downlinkshared channel (DL-SCH) being one of the transport channels shown inFIG. 5 described below, resource allocation information for a pagingchannel (PCH) being one of the transport channels shown in FIG. 5, andhybrid automatic repeat request (HARM) information related to DL-SCH.The PDCCH carries an uplink scheduling grant. The PDCCH carriesacknowledgement (Ack)/negative acknowledgement (Nack) that is a responsesignal to uplink transmission. The PDCCH is referred to as an L1/L2control signal as well.

A physical downlink shared channel (PDSCH) 404 is a channel for downlinktransmission from the base station 102 to the user equipment 101. Adownlink shared channel (DL-SCH) that is a transport channel and a PCHthat is a transport channel are mapped to the PDSCH.

A physical multicast channel (PMCH) 405 is a channel for downlinktransmission from the base station 102 to the user equipment 101. Amulticast channel (MCH) that is a transport channel is mapped to thePMCH.

A physical uplink control channel (PUCCH) 406 is a channel for uplinktransmission from the user equipment 101 to the base station 102. ThePUCCH carries Ack/Nack that is a response signal to downlinktransmission. The PUCCH carries a channel quality indicator (CQI)report. The CQI is quality information indicating the quality ofreceived data or channel quality. In addition, the PUCCH carries ascheduling request (SR).

A physical uplink shared channel (PUSCH) 407 is a channel for uplinktransmission from the user equipment 101 to the base station 102. Anuplink shared channel (UL-SCH) that is one of the transport channelsshown in FIG. 5 is mapped to the PUSCH.

A physical hybrid ARQ indicator channel (PHICH) 408 is a channel fordownlink transmission from the base station 102 to the user equipment101. The PHICH carries Ack/Nack that is a response signal to uplinktransmission. A physical random access channel (PRACH) 409 is a channelfor uplink transmission from the user equipment 101 to the base station102. The PRACH carries a random access preamble.

A downlink reference signal (RS) is a known symbol in the LTEcommunication system. The following five types of downlink referencesignals are defined: cell-specific reference signals (CRSs), MBSFNreference signals, data demodulation reference signals (DM-RSs) beingUE-specific reference signals, positioning reference signals (PRSs), andchannel-state information reference signals (CSI-RSs). The physicallayer measurement objects of a user equipment include reference symbolreceived power (RSRP).

The transport channels described in Non-Patent Document 1 (Chapter 5)will be described with reference to FIG. 5. FIG. 5 is a diagramillustrating transport channels used in the LTE communication system.FIG. 5(A) shows mapping between downlink transport channels and downlinkphysical channels. FIG. 5(B) shows mapping between uplink transportchannels and uplink physical channels.

A broadcast channel (BCH) among the downlink transport channels shown inFIG. 5(A) is broadcast to the entire coverage of a base station (cell).The BCH is mapped to the physical broadcast channel (PBCH).

Retransmission control according to a hybrid ARQ (HARM) is applied to adownlink shared channel (DL-SCH). The DL-SCH enables broadcast to theentire coverage of the base station (cell). The DL-SCH supports dynamicor semi-static resource allocation. The semi-static resource allocationis also referred to as persistent scheduling. The DL-SCH supportsdiscontinuous reception (DRX) of a user equipment for enabling the userequipment to save power. The DL-SCH is mapped to the physical downlinkshared channel (PDSCH).

The paging channel (PCH) supports DRX of the user equipment for enablingthe user equipment to save power. The PCH is required to broadcast tothe entire coverage of the base station (cell). The PCH is mapped tophysical resources such as the physical downlink shared channel (PDSCH)that can be used dynamically for traffic.

The multicast channel (MCH) is used for broadcast to the entire coverageof the base station (cell). The MCH supports SFN combining of MBMSservices (MTCH and MCCH) in multi-cell transmission. The MCH supportssemi-static resource allocation. The MCH is mapped to the PMCH.

Retransmission control according to a hybrid ARQ (HARQ) is applied to anuplink shared channel (UL-SCH) among the uplink transport channels shownin FIG. 5(B). The UL-SCH supports dynamic or semi-static resourceallocation. The UL-SCH is mapped to the physical uplink shared channel(PUSCH).

A random access channel (RACH) shown in FIG. 5(B) is limited to controlinformation. The RACH involves a collision risk. The RACH is mapped tothe physical random access channel (PRACH).

The HARQ will be described. The HARQ is the technique for improving thecommunication quality of a channel by combination of automatic repeatrequest (ARQ) and error correction (forward error correction). The HARQis advantageous in that error correction functions effectively byretransmission even for a channel whose communication quality changes.In particular, it is also possible to achieve further qualityimprovement in retransmission through combination of the receptionresults of the first transmission and the reception results of theretransmission.

An example of the retransmission method will be described. In a casewhere the receiver fails to successfully decode the received data, inother words, in a case where a cyclic redundancy check (CRC) erroroccurs (CRC=NG), the receiver transmits “Nack” to the transmitter. Thetransmitter that has received “Nack” retransmits the data. In a casewhere the receiver successfully decodes the received data, in otherwords, in a case where a CRC error does not occur (CRC=OK), the receivertransmits “AcK” to the transmitter. The transmitter that has received“Ack” transmits the next data.

Examples of the HARQ system include chase combining. In chase combining,the same data is transmitted in the first transmission andretransmission, which is the system for improving gains by combining thedata of the first transmission and the data of the retransmission inretransmission. Chase combining is based on the idea that correct datais partially included even if the data of the first transmissioncontains an error, and highly accurate data transmission is enabled bycombining the correct portions of the first transmission data and theretransmission data. Another example of the HARQ system is incrementalredundancy (IR). The IR is aimed to increase redundancy, where a paritybit is transmitted in retransmission to increase the redundancy bycombining the first transmission and retransmission, to thereby improvethe quality by an error correction function.

The logical channels described in Non-Patent Document 1 (Chapter 6) willbe described with reference to FIG. 6. FIG. 6 is a diagram illustratinglogical channels used in an LTE communication system. FIG. 6(A) showsmapping between downlink logical channels and downlink transportchannels. FIG. 6(B) shows mapping between uplink logical channels anduplink transport channels.

A broadcast control channel (BCCH) is a downlink channel for broadcastsystem control information. The BCCH that is a logical channel is mappedto the broadcast channel (BCH) or downlink shared channel (DL-SCH) thatis a transport channel.

A paging control channel (PCCH) is a downlink channel for transmittingpaging signals and system information change notifications. The PCCH isused when the network does not know the cell location of a userequipment. The PCCH that is a logical channel is mapped to the pagingchannel (PCH) that is a transport channel.

A common control channel (CCCH) is a channel for transmission controlinformation between user equipments and a base station. The CCCH is usedin a case where the user equipments have no RRC connection with thenetwork. In a downlink direction, the CCCH is mapped to the downlinkshared channel (DL-SCH) that is a transport channel. In an uplinkdirection, the CCCH is mapped to the uplink shared channel (UL-SCH) thatis a transport channel.

A multicast control channel (MCCH) is a downlink channel forpoint-to-multipoint transmission. The MCCH is used for transmission ofMBMS control information for one or several MTCHs from a network to auser equipment. The MCCH is used only by a user equipment duringreception of the MBMS. The MCCH is mapped to the multicast channel (MCH)that is a transport channel.

A dedicated control channel (DCCH) is a point-to-point channel thattransmits dedicated control information between a user equipment and anetwork. The DCCH is used if the user equipment has an RRC connection.The DCCH is mapped to the uplink shared channel (UL-SCH) in uplink andmapped to the downlink shared channel (DL-SCH) in downlink.

A dedicated traffic channel (DTCH) is a point-to-point communicationchannel for transmission of user information to a dedicated userequipment. The DTCH exists in uplink as well as downlink. The DTCH ismapped to the uplink shared channel (UL-SCH) in uplink and mapped to thedownlink shared channel (DL-SCH) in downlink.

A multicast traffic channel (MTCH) is a downlink channel for trafficdata transmission from a network to a user equipment. The MTCH is achannel used only by a user equipment during reception of the MBMS. TheMTCH is mapped to the multicast channel (MCH).

CGI represents a cell global identifier. ECGI represents an E-UTRAN cellglobal identifier. A closed subscriber group (CSG) cell is introduced inthe LTE, and the long term evolution advanced (LTE-A) and universalmobile telecommunication system (UMTS) described below. The CSG will bedescribed below (see Chapter 3.1 of Non-Patent Document 3).

The closed subscriber group (CSG) cell is a cell in which subscriberswho are allowed to use are specified by an operator (also referred to asa “cell for specific subscribers”). The specified subscribers areallowed to access one or more cells of a public land mobile network(PLMN). One or more cells in which the specified subscribers are allowedaccess are referred to as “CSG cell(s)”. Note that access is limited inthe PLMN.

The CSG cell is part of the PLMN that broadcasts a specific CSG identity(CSG ID; CSG-ID) and broadcasts “TRUE” in a CSG indication. Theauthorized members of the subscriber group who have registered inadvance access the CSG cells using the CSG-ID that is the accesspermission information.

The CSG-ID is broadcast by the CSG cell or cells. A plurality of CSG-IDsexist in the LTE communication system. The CSG-IDs are used by userequipments (UEs) for making access from CSG-related members easier.

The locations of user equipments are tracked based on an area composedof one or more cells. The locations are tracked for enabling tracking ofthe locations of user equipments and calling user equipments, in otherwords, incoming calling to user equipments) even in an idle state. Anarea for tracking locations of user equipments is referred to as atracking area.

The CSG whitelist is a list that may be stored in a universal subscriberidentity module (USIM) in which all CSG IDs of the CSG cells to whichthe subscribers belong are recorded. The CSG whitelist may be merelyreferred to as a whiltelist or an allowed CSG list as well. As to theaccess of user equipments through a CSG cell, the MME performs accesscontrol (see Chapter 4.3.1.2 of Non-Patent Document 4). Specificexamples of the access of user equipments include attach, combinedattach, detach, service request, and a tracking area update procedure(see Chapter 4.3.1.2 of Non-Patent Document 4).

The service types of a user equipment in an idle state will be describedbelow (see Chapter 4.3 of Non-Patent Document 3). The service types ofuser equipments in an idle state include a limited service, standardservice (normal service), and operator service. The limited serviceincludes emergency calls, earthquake and tsunami warning system (ETWS),and commercial mobile alert system (CMAS) on an acceptable celldescribed below. The standard service (also referred to as normalservice) is a public service on a suitable cell described below. Theoperator service includes a service for operators only on a reservedcell described below.

A “suitable cell” will be described below. The “suitable cell” is a cellon which a UE may camp to obtain normal service. Such a cell shallfulfill the following conditions (1) and (2).

(1) The cell is part of the selected PLMN or the registered PLMN, orpart of the PLMN of an “equivalent PLMN list.”

(2) According to the latest information provided by a non-access stratum(NAS), the cell shall further fulfill the following conditions (a) to(d):

(a) the cell is not a barred cell;

(b) the cell is part of a tracking area (TA), not part of the list of“forbidden LAs for roaming,” where the cell needs to fulfill (1) above;

(c) the cell shall fulfill the cell selection criteria; and

(d) for a cell specified as CSG cell by system information (SI), theCSG-ID is part of a “CSG whitelist” of the UE, that is, is contained inthe CSG whitelist of the UE.

An “acceptable cell” will be described below. The “acceptable cell” is acell on which a UE may camp to obtain limited service. Such a cell shallfulfill the all following requirements.

(1) The cell is not a prohibited cell (also referred to as a “barredcell”).

(2) The cell fulfills the cell selection criteria.

“Barred cell” is indicated in the system information. “Reserved cell” isindicated in the system information.

“Camping on a cell” represents the state where a UE has completed thecell selection/cell reselection process and the UE has selected a cellfor monitoring the system information and paging information. The cellon which the UE camps may be referred to as a “serving cell.”

3GPP is studying base stations referred to as Home-NodeB (Home-NB; HNB)and Home-eNodeB (Home-eNB; HeNB). HNB/HeNB is a base station for, forexample, household, corporation, or commercial access service inUTRAN/E-UTRAN.

Non-Patent Document 5 discloses three different modes of the access tothe HeNB and HNB. Specifically, those are an open access mode, a closedaccess mode, and a hybrid access mode.

The respective modes have the following characteristics. In the openaccess mode, the HeNB and HNB are operated as a normal cell of a normaloperator. In the closed access mode, the HeNB and HNB are operated as aCSG cell. The CSG cell is a CSG cell where only CSG members are allowedaccess. In the hybrid access mode, the HeNB and HNB are operated as CSGcells where non-CSG members are allowed access at the same time. Inother words, a cell in the hybrid access mode (also referred to as ahybrid cell) is a cell that supports both the open access mode and theclosed access mode.

In 3GPP, among all physical cell identities (PCIs), there is a range ofPCIs reserved by the network for use by CSG cells (see Chapter 10.5.1.1of Non-Patent Document 1). Division of the PCI range is also referred toas PCI split. The information about PCI split (also referred to as PCIsplit information) is broadcast in the system information from a basestation to user equipments being served thereby. To being served by abase station means to take the base station as a serving cell.

Non-Patent Document 6 discloses the basic operation of a user equipmentusing PCI split. The user equipment that does not have the PCI splitinformation needs to perform cell search using all PCIs, for example,using all 504 codes. On the other hand, the user equipment that has thePCI split information is capable of performing cell search using the PCIsplit information.

Further, 3GPP is pursuing specifications standard of long term evolutionadvanced (LTE-A) as Release 10 (see Non-Patent Documents 7 and 8).

As to the LTE-A system, it is studied that a relay and a relay node (RN)are supported for achieving a high data rate, high cell-edge throughput,new coverage area, and the like. The relay node is wirelessly connectedto the radio-access network via a cell referred to as a donor cell(hereinafter, also referred to as a “Donor eNB; DeNB”). The network(NW)-to-relay node link shares the same frequency band with thenetwork-to-UE link within the range of the donor cell. In this case, theUE supporting Release 8 of 3GPP can also be connected to the donor cell.The link between a donor cell and a relay node is referred to as abackhaul link, and the link between the relay node and the UE isreferred to as an access link.

As the method of multiplexing a backhaul link in frequency divisionduplex (FDD), the transmission from a DeNB to an RN is performed at adownlink (DL) frequency band, and the transmission from an RN to a DeNBis performed at an uplink (UL) frequency band. As the method of dividingresources in a relay, a link from a DeNB to an RN and a link from an RNto a UE are time-division multiplexed at one frequency band, and a linkfrom an RN to a DeNB and a link from a UE to an RN are alsotime-division multiplexed at one frequency band. In a relay,accordingly, the transmission of the relay is prevented from interferingthe reception of the own relay.

Not only a normal eNB (macro cell) but also so-called local nodes suchas pico eNB (pico cell), HeNB (HNB, CSG cell), node for hotzone cells,relay node, remote radio head (RRH), and repeater are studied in 3GPP.The network composed of various types of cells as described above isalso referred to as a heterogeneous network (HetNet) in some cases.

The frequency bands (hereinafter, also referred to as “operating bands”)usable for communication have been predetermined in the LTE. Non-PatentDocument 9 describes the frequency bands.

Carrier aggregation (CA) is studied in the LTE-A system, in which two ormore component carriers (CCs) are aggregated to support widertransmission bandwidths up to 100 MHz.

A Release 8 or 9 of 3GPP-compliant UE, which supports LTE, is capable oftransmission/reception only on one CC corresponding to one serving cell.Meanwhile, it is conceivable that a Release 10 of 3GPP-compliant UE mayhave the capability of transmission and reception, only reception, oronly transmission on a plurality of CCs corresponding to a plurality ofserving cells at the same time.

Each CC employs the configuration of Release 8 or 9 of 3GPP, and the CAsupports contiguous CCs, non-contiguous CCs, and CCs in differentfrequency bandwidths. The UE cannot configure the number of uplink CCs(UL CCs) more than the number of downlink CCs (DL CCs). The CCsconfigured by the same eNBs do not need to provide the same coverage.The CC is compatible with Release 8 or 9.

In CA, an independent HARQ entity is provided per serving cell in uplinkas well as downlink. A transport block is generated per TTI for eachserving cell. Each transport block and HARQ retransmission are mapped toa single serving cell.

In a case where CA is configured, a UE has single RRC connection with aNW. In RRC connection, one serving cell provides NAS mobilityinformation and security input. This cell is referred to as a primarycell (PCell). In downlink, a carrier corresponding to PCell is adownlink primary component carrier (DL PCC). In uplink, a carriercorresponding to PCell is an uplink primary component carrier (UL PCC).

A secondary cell (SCell) is configured to form a pair of a PCell and aserving cell, in accordance with the UE capability. In downlink, acarrier corresponding to SCell is a downlink secondary component carrier(DL SCC). In uplink, a carrier corresponding to SCell is an uplinksecondary component carrier (UL SCC).

A pair of one PCell and a serving cell configured by one or more SCellsis configured for one UE.

The above-mentioned LTE Advanced (LTE-A) is studied as a furtheradvanced communication system regarding radio areas in 3GPP (seeNon-Patent Documents 7 and 8). The LTE-A is based on the LTEcommunication system regarding radio areas and is configured by additionof several new techniques thereto. The new techniques include thetechnique of supporting wider bands (wider bandwidth extension) and thecoordinated multiple point transmission and reception (CoMP) technique.The CoMP studied for LTE-A in 3GPP is described in Non-Patent Document10.

CoMP is the technique of improving the coverage of high data rates,improving a cell-edge throughput, and increasing a communication systemthroughput by transmission or reception coordinated among multiplegeographically separated points. The CoMPs are grouped into downlinkCoMP (DL CoMP) and uplink CoMP (UL CoMP).

In DL CoMP, the PDSCH to one user equipment (UE) is transmitted incooperation among multiple points. The PDSCH to one UE may betransmitted from one point among multiple points or may be transmittedfrom points among multiple points. In DL CoMP, a serving cell refers toa single cell that transmits resource allocation over the PDCCH.

Joint processing (JP) and coordinated scheduling (CS)/coordinatedbeamforming (CB) (hereinafter, also referred to as “CS/CB”) are studiedas the DL CoMP method.

For JP, data is available at each point in a CoMP cooperating set. JPsare grouped into joint transmission (JT) and dynamic point selection(DPS). The DPS includes dynamic cell selection (DCS). In JT, the PDSCHis transmitted from multiple points, specifically, part of or the entireCoMP cooperating set, at a time. In DPS, the PDSCH is transmitted fromone point in the CoMP cooperating set at a time.

In CS/CB, data is only available in transmission from a serving cell. InCS/CB, user scheduling or beamforming decisions are made withcoordination among cells corresponding to the CoMP cooperating set.

Base stations (NB, eNB, HNB, HeNB), remote radio unit (RRU), remoteradio equipment (RRE), remote radio head (RRH), relay node (RN), and thelike are studied as the units and cells that perform transmission andreception at multiple points. The unit and cell that perform coordinatedmultiple point transmission are referred to as a multi-point unit and amulti-point cell, respectively.

3GPP is pursuing specifications standard of Release 11. As to thisspecification, additional carrier types that are new items to bedeveloped are discussed for improved frequency use efficiency, improvedsupport for HetNet, and energy saving of a system (see Non-PatentDocument 11). Hereinafter, the additional carrier type is referred to asa new carrier type (NCT).

PRIOR ART DOCUMENTS Non-Patent Documents

-   Non-Patent Document 1: 3GPP TS 36.300 V11.2.0-   Non-Patent Document 2: 3GPP TS 36.331 V11.0.0-   Non-Patent Document 3: 3GPP TS 36.304 V11.0.0 Chapter 3.1, Chapter    4.3, Chapter 5.2.4-   Non-Patent Document 4: 3GPP TR 23.830 V9.0.0-   Non-Patent Document 5: 3GPP S1-083461-   Non-Patent Document 6: 3GPP R2-082899-   Non-Patent Document 7: 3GPP TR 36.814 V9.0.0-   Non-Patent Document 8: 3GPP TR 36.912 V10.0.0-   Non-Patent Document 9: 3GPP TS 36.101 V11.0.0-   Non-Patent Document 10: 3GPP TR 36.819 V11.1.0-   Non-Patent Document 11: 3GPP RAN1 #66BIS meeting report

SUMMARY OF INVENTION Problem to be Solved by the Invention

As described above, NCTs are currently under discussion of 3GPP, andthus, for example, the method of operating a communication systemsuitable for NCTs has yet to be established. Therefore, such a techniqueis desired that establishes the method of operating a communicationsystem suitable for NCTs to normally and efficiently operate thecommunication systems of Release 11 and the following releases in whichexisting carriers (hereinafter, also referred to as “legacy carriers”)and NCTs coexist.

The present invention has an object to provide a communication systemthat can be normally and efficiently operated in the case where existingcarriers and new carrier types coexist.

Means to Solve the Problem

A communication system according to the present invention is acommunication system in which a base station device and a communicationterminal device are configured to communicate with each other in a firstcell configured on a predetermined first carrier, wherein the basestation device includes a second cell configured on a second carrierdifferent from the first carrier, the second carrier is associated withthe first carrier belonging to the same frequency band as a frequencyband of the second carrier, and an associated carrier being the firstcarrier associated with the second carrier notifies the communicationterminal device of carrier information being information on the secondcarrier.

Effects of the Invention

According to the communication system of the present invention, acommunication system in which a first carrier and a second carriercoexist can be uniformly and normally operated. In addition, anassociated carrier and the second carrier belong to the same frequencyband, which merely requires the communication terminal device to operatea wireless unit for one frequency band for receiving the associatedcarrier and the second carrier. The power consumption of thecommunication terminal device can be therefore reduced.

These and other objects, features, aspects and advantages of the presentinvention will become more apparent from the following detaileddescription of the present invention when taken in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating the configuration of an LTEcommunication system.

FIG. 2 is a diagram illustrating the configuration of a radio frame usedin the LTE communication system.

FIG. 3 is a diagram illustrating the configuration of an MBSFN frame.

FIG. 4 is a diagram illustrating physical channels used in the LTEcommunication system.

FIG. 5 is a diagram illustrating transport channels used in the LTEcommunication system.

FIG. 6 is a diagram illustrating logical channels used in the LTEcommunication system.

FIG. 7 is a block diagram showing the overall configuration of an LTEcommunication system currently under discussion of 3GPP.

FIG. 8 is a block diagram showing the configuration of a user equipment71 of FIG. 7 being a user equipment according to the present invention.

FIG. 9 is a block diagram showing the configuration of a base station 72of FIG. 7 being a base station according to the present invention.

FIG. 10 is a block diagram showing the configuration of an MME unit 73of FIG. 7 being an MME according to the present invention.

FIG. 11 is a block diagram showing the configuration of a HeNBGW 74 ofFIG. 7 being a HeNBGW according to the present invention.

FIG. 12 is a flowchart showing an outline from a cell search to an idlestate operation performed by a user equipment (UE) in the LTEcommunication system.

FIG. 13 shows the concept of a solution in a first embodiment of thepresent invention.

FIG. 14 shows an example architecture of an NCT.

FIG. 15 shows an architecture of an existing cell.

FIG. 16 shows the concept of co-channel deployment of an NCT.

FIG. 17 shows an example sequence in a case where a specific example (1)is used as an entity that configures an NCT for a UE in a communicationsystem according to a second modification of the first embodiment of thepresent invention.

FIG. 18 shows an example sequence in a case where a specific example (2)is used as the entity that configures an NCT for a UE in thecommunication system according to the second modification of the firstembodiment of the present invention.

FIG. 19 shows an example sequence in the case where the specific example(2) is used as the entity that configures an NCT for a UE in thecommunication system according to the second modification of the firstembodiment of the present invention.

FIG. 20 shows an example sequence in a case where a specific example (3)is used as the entity that configures an NCT for a UE in thecommunication system according to the second modification of the firstembodiment of the present invention.

FIG. 21 shows an example sequence in a case where a specific example (4)is used as the entity that configures an NCT for a UE in thecommunication system according to the second modification of the firstembodiment of the present invention.

FIG. 22 shows an example sequence in a case where a specific example (1)of a method of determining an associated legacy carrier in a semi-staticor dynamic manner in a communication system according to a thirdmodification of the first embodiment of the present invention.

FIG. 23 shows an example sequence in a case where a specific example (2)of the method of determining an associated legacy carrier in asemi-static or dynamic manner in the communication system according tothe third modification of the first embodiment of the present invention.

FIG. 24 shows an example sequence in a case where a specific example (1)is used as a cross-carrier scheduling method suitable for an NCT in acommunication system according to a second embodiment of the presentinvention.

FIG. 25 shows an example sequence in a case where a specific example (2)is used as the cross-carrier scheduling method suitable for an NCT inthe communication system according to the second embodiment of thepresent invention.

FIG. 26 shows an example sequence in a case where a specific example (3)is used as the cross-carrier scheduling method suitable for an NCT inthe communication system according to the second embodiment of thepresent invention.

FIG. 27 shows the concept of a solution (1) in a first modification ofthe second embodiment of the present invention.

FIG. 28 shows the concept of a solution (2) in the first modification ofthe second embodiment of the present invention.

FIG. 29 shows the concept of the solution (2) in the first modificationof the second embodiment of the present invention.

FIG. 30 shows the concept of a solution in a second modification of thesecond embodiment of the present invention.

FIG. 31 shows an example sequence of a communication system in asolution (1) of a third embodiment of the present invention.

FIG. 32 shows an example sequence of a communication system in asolution (2) of the third embodiment of the present invention.

FIG. 33 shows an example sequence in a case where a specific method (1)of operating an eNB1 and an eNB2 is used in a communication systemaccording to a first modification of the third embodiment of the presentinvention.

FIG. 34 shows an example sequence in a case where specific methods (2)and (3) of operating an eNB1 and an eNB2 are used in combination in thecommunication system according to the first modification of the thirdembodiment of the present invention.

FIG. 35 shows an example sequence in a case where a specific example (1)of a notification method and a specific example (1) of a request methodare used in combination in a communication system of a fourth embodimentof the present invention.

FIG. 36 shows an example sequence in a case where a specific example (2)of the notification method and a specific example (2) of the requestmethod are used in combination in the communication system of the fourthembodiment of the present invention.

FIG. 37 shows an example sequence in a communication system in asolution of a first modification of the fourth embodiment of the presentinvention.

DESCRIPTION OF EMBODIMENTS First Embodiment

FIG. 7 is a block diagram showing an overall configuration of an LTEcommunication system, which is currently under discussion of 3GPP. 3GPPis studying an overall configuration of a system including closedsubscriber group (CSG) cells (Home-eNodeBs (Home-eNB; HeNB) of E-UTRAN,Home-NB (HNB) of UTRAN) and non-CSG cells (eNodeB (eNB) of E-UTRAN,NodeB (NB) of UTRAN, and BSS of GERAN) and, as to E-UTRAN, is proposingthe configuration as shown in FIG. 7 (see Chapter 4.6.1 of Non-PatentDocument 1).

FIG. 7 will be described. A mobile terminal device being a communicationterminal device (hereinafter, referred to as a “user equipment” or “UE”)71 is capable of performing radio communication with a base stationdevice (hereinafter, referred to as a “base station”) 72 andtransmits/receives signals through radio communication. The basestations 72 are classified into an eNB 72-1 that is a macro cell and aHome-eNB 72-2 that is a local node. The eNB 72-1 has a relativelylarge-scale coverage as the coverage in a range in which communicationis allowed with the user equipment (UE) 71. The Home-eNB 72-2 has arelatively small-scale coverage as the coverage.

The eNB 72-1 is connected to an MME/S-GW unit (hereinafter, alsoreferred to as an “MME unit”) 73 including an MME, S-GW, or MME and S-GWthrough an S1 interface, and control information is communicated betweenthe eNB 72-1 and the MME unit 73. A plurality of MME units 73 may beconnected to one eNB 72-1. The MME unit 73 is included in an EPC being acore network. The eNBs 72-1 are connected to each other by means of anX2 interface, and control information is communicated between the eNBs72-1.

The Home-eNB 72-2 is connected to the MME unit 73 by means of an S1interface, and control information is communicated between the Home-eNB72-2 and the MME unit 73. A plurality of Home-eNBs 72-2 are connected toone MME unit 73. Or, the Home-eNBs 72-2 are connected to the MME units73 through a Home-eNB Gateway (HeNBGW) 74. The Home-eNBs 72-2 areconnected to the HeNBGW 74 by means of the S1 interface, and the HeNBGW74 is connected to the MME units 73 through an S1 interface.

One or a plurality of Home-eNBs 72-2 are connected to one HeNBGW 74, andinformation is communicated therebetween through an S1 interface. TheHeNBGW 74 is connected to one or a plurality of MME units 73, andinformation is communicated therebetween through an S1 interface.

The MME units 73 and HeNBGW 74 are devices of higher nodes and controlthe connection between the user equipment (UE) 71 and the eNB 72-1 orHome-eNB 72-2 being a base station. The MME units 73 and HeNBGW areincluded in an EPC being a core network.

Further, 3GPP is currently studying the configuration below. The X2interface between the Home-eNBs 72-2 is supported. In other words, theHome-eNBs 72-2 are connected to each other by means of an X2 interface,and control information is communicated between the Home-eNBs 72-2. TheHeNBGW 74 appears to the MME unit 73 as the Home-eNB 72-2. The HeNBGW 74appears to the Home-eNB 72-2 as the MME unit 73.

The interfaces between the Home-eNBs 72-2 and the MME units 73 are thesame, which are the S1 interfaces, in both cases where the Home-eNB 72-2is connected to the MME unit 73 through the HeNBGW 74 and it is directlyconnected to the MME unit 73. The mobility to the Home-eNB 72-2 or themobility from the Home-eNB 72-2 that spans a plurality of MME units 73is not supported. The Home-eNB 72-2 is configured by a single cell.

The base station device is configured by a single cell alone, such asthe Home-eNB 72-2, which is not limited thereto. One base station devicemay be configured by a plurality of cells. In a case where one basestation device is configured by a plurality of cells, every cell isconfigured to communicate with a user equipment.

FIG. 8 is a block diagram showing the configuration of the userequipment 71 of FIG. 7 being a user equipment according to the presentinvention. The transmission process of the user equipment 71 shown inFIG. 8 will be described. First, a transmission data buffer unit 803stores the control data from a protocol processing unit 801 and the userdata from an application unit 802. The data stored in the transmissiondata buffer unit 803 is transmitted to an encoding unit 804 and issubjected to an encoding process such as error correction. There mayexist the data output from the transmission data buffer unit 803directly to a modulating unit 805 without the encoding process. The dataencoded by the encoding unit 804 is modulated by the modulating unit805. The modulated data is output to a frequency converting unit 806after being converted into a baseband signal, and is then converted intoa radio transmission frequency. After that, a transmission signal istransmitted from an antenna 807 to the base station 72.

The user equipment 71 executes the reception process as follows. Theradio signal is received through the antenna 807 from the base station72. The received signal is converted from a radio reception frequencyinto a baseband signal by the frequency converting unit 806 and is thendemodulated by a demodulating unit 808. The demodulated data istransmitted to a decoding unit 809 and is subjected to a decodingprocess such as error correction. Among the pieces of decoded data, thecontrol data is transmitted to the protocol processing unit 801, whilethe user data is transmitted to the application unit 802. A series ofprocesses of the user equipment 71 is controlled by a control unit 810.This means that, though not shown in FIG. 8, the control unit 810 isconnected to the respective units 801 to 809.

FIG. 9 is a block diagram showing the configuration of the base station72 of FIG. 7 being a base station according to the present invention.The transmission process of the base station 72 shown in FIG. 9 will bedescribed. An EPC communication unit 901 performs datatransmission/reception between the base station 72 and the EPCs (such asthe MME unit 73 and the HeNBGW 74). A communication with another basestation unit 902 performs data transmission/reception to/from anotherbase station. The EPC communication unit 901 and the communication withanother base station unit 902 respectively transmit/receive informationto/from a protocol processing unit 903. The control data from theprotocol processing unit 903, and the user data and control data fromthe EPC communication unit 901 and the communication with another basestation unit 902 are stored in a transmission data buffer unit 904.

The data stored in the transmission data buffer unit 904 is transmittedto an encoding unit 905 and is then subjected to an encoding processsuch as error correction. There may exist the data output from thetransmission data buffer unit 904 directly to a modulating unit 906without the encoding process. The encoded data is modulated by themodulating unit 906. The modulated data is output to a frequencyconverting unit 907 after being converted into a baseband signal, and isthen converted into a radio transmission frequency. After that, atransmission signal is transmitted from an antenna 908 to one or aplurality of user equipments 71.

The reception process of the base station 72 is executed as follows. Aradio signal from one or a plurality of user equipments 71 is receivedthrough the antenna 908. The received signal is converted from a radioreception frequency into a baseband signal by the frequency convertingunit 907, and is then demodulated by a demodulating unit 909. Thedemodulated data is transmitted to a decoding unit 910 and is thensubjected to a decoding process such as error correction. Among thepieces of decoded data, the control data is transmitted to the protocolprocessing unit 903, EPC communication unit 901, or communication withanother base station unit 902, while the user data is transmitted to theEPC communication unit 901 and the communication with another basestation unit 902. A series of processes by the base station 72 iscontrolled by a control unit 911. This means that, though not shown inFIG. 9, the control unit 911 is connected to the respective units 901 to910.

The functions of the Home-eNB 72-2 currently under discussion of 3GPPwill be described below (see Chapter 4.6.2 of Non-Patent Document 1).The Home-eNB 72-2 has the same function as that of the eNB 72-1. Inaddition, the Home-eNB 72-2 has the function of discovering a suitableserving HeNBGW 74 in a case of connection to the HeNBGW 74. The Home-eNB72-2 is connected only to one HeNBGW 74. That is, in a case of theconnection to the HeNBGW 74, the Home-eNB 72-2 does not use the Flexfunction in the S1 interface. When the Home-eNB 72-2 is connected to oneHeNBGW 74, it is not simultaneously connected to another HeNBGW 74 andanother MME unit 73.

The tracking area code (TAC) and PLMN ID of the Home-eNB 72-2 aresupported by the HeNBGW 74. When the Home-eNB 72-2 is connected to theHeNBGW 74, selection of the MME unit 73 at “UE attachment” is performedby the HeNBGW 74 instead of the Home-eNB 72-2. The Home-eNB 72-2 may bedeployed without network planning. In this case, the Home-eNB 72-2 ismoved from one geographical area to another geographical area. TheHome-eNB 72-2 in this case is accordingly required to be connected to adifferent HeNBGW 74 depending on its location.

FIG. 10 is a block diagram showing the configuration of the MMEaccording to the present invention. FIG. 10 shows the configuration ofan MME 73 a included in the MME unit 73 shown in FIG. 7 described above.A PDN GW communication unit 1001 performs data transmission/receptionbetween the MME 73 a and a PDN GW. A base station communication unit1002 performs data transmission/reception between the MME 73 a and thebase station 72 by means of the S1 interface. In the case where the datareceived from the PDN GW is user data, the user data is transmitted fromthe PDN GW communication unit 1001 to the base station communicationunit 1002 through a user plane communication unit 1003 and is thentransmitted to one or a plurality of base stations 72. In the case wherethe data received from the base station 72 is user data, the user datais transmitted from the base station communication unit 1002 to the PDNGW communication unit 1001 through the user plane communication unit1003 and is then transmitted to the PDN GW.

In the case where the data received from the PDN GW is control data, thecontrol data is transmitted from the PDN GW communication unit 1001 to acontrol plane control unit 1005. In the case where the data receivedfrom the base station 72 is control data, the control data istransmitted from the base station communication unit 1002 to the controlplane control unit 1005.

A HeNBGW communication unit 1004 is provided in the case where theHeNBGW 74 is provided, which performs data transmission/reception of theinterface (IF) between the MME 73 a and the HeNBGW 74 according to aninformation type. The control data received from the HeNBGWcommunication unit 1004 is transmitted from the HeNBGW communicationunit 1004 to the control plane control unit 1005. The processing resultsof the control plane control unit 1005 are transmitted to the PDN GWthrough the PDN GW communication unit 1001. The processing results ofthe control plane control unit 1005 are transmitted to one or aplurality of base stations 72 by means of the S1 interface through thebase station communication unit 1002, and are transmitted to one or aplurality of HeNBGWs 74 through the HeNBGW communication unit 1004.

The control plane control unit 1005 includes a NAS security unit 1005-1,an SAE bearer control unit 1005-2, an idle state mobility managing unit1005-3, and other unit, and performs overall process for the controlplane. The NAS security unit 1005-1 provides, for example, security of anon-access stratum (NAS) message. The SAE bearer control unit 1005-2manages, for example, a system architecture evolution (SAE) bearer. Theidle state mobility managing unit 1005-3 performs, for example, mobilitymanagement of an idle state (LTE-IDLE state, which is merely referred toas idle as well), generation and control of a paging signal in an idlestate, addition, deletion, update, and search of a tracking area (TA) ofone or a plurality of user equipments 71 being served thereby, andtracking area list management.

The MME 73 a begins a paging protocol by transmitting a paging messageto the cell belonging to a tracking area (TA) in which the UE isregistered. The idle state mobility managing unit 1005-3 may manage theCSG of the Home-eNBs 72-2 to be connected to the MME 73 a, CSG-IDs, anda whitelist.

In the CSG-ID management, the relationship between a user equipmentcorresponding to the CSG-ID and the CSG cell is managed (for example,added, deleted, updated, or searched). For example, the relationship maybe the relationship between one or a plurality of user equipments whoseuser access registration has been performed with a CSG-ID and the CSGcells belonging to this CSG-ID. In the whitelist management, therelationship between the user equipment and the CSG-ID is managed (forexample, added, deleted, updated, or searched). As an example, one or aplurality of CSG-IDs with which user registration has been performed bya user equipment may be stored in the whitelist. The above-mentionedmanagement related to the CSG may be performed by another part of theMME 73 a. A series of processes by the MME 73 a is controlled by acontrol unit 1006. This means that, though not shown in FIG. 10, thecontrol unit 1006 is connected to the respective units 1001 to 1005.

The function of the MME 73 a currently under discussion of 3GPP will bedescribed below (see Chapter 4.6.2 of Non-Patent Document 1). The MME 73a performs access control for one or a plurality of user equipmentsbeing members of closed subscriber groups (CSGs). The MME 73 arecognizes the execution of paging optimization as an option.

FIG. 11 is a block diagram showing the configuration of the HeNBGW 74shown in FIG. 7 that is a HeNBGW according to the present invention. AnEPC communication unit 1101 performs data transmission/reception betweenthe HeNBGW 74 and the MME 73 a by means of the S1 interface. A basestation communication unit 1102 performs data transmission/receptionbetween the HeNBGW 74 and the Home-eNB 72-2 by means of the S1interface. A location processing unit 1103 performs the process oftransmitting, to a plurality of Home-eNBs 72-2, the registrationinformation or the like among the pieces of data transmitted from theMME 73 a through the EPC communication unit 1101. The data processed bythe location processing unit 1103 is transmitted to the base stationcommunication unit 1102 and is transmitted to one or a plurality ofHome-eNBs 72-2 through the S1 interface.

The data only caused to pass through (to be transparent) withoutrequiring the process by the location processing unit 1103 is passedfrom the EPC communication unit 1101 to the base station communicationunit 1102, and is transmitted to one or a plurality of Home-eNBs 72-2through the S1 interface. A series of processes by the HeNBGW 74 iscontrolled by a control unit 1104. This means that, though not shown inFIG. 11, the control unit 1104 is connected to the respective units 1101to 1103.

The function of the HeNBGW 74 currently under discussion of 3GPP will bedescribed below (see Chapter 4.6.2 of Non-Patent Document 1). The HeNBGW74 relays an S1 application. The HeNBGW 74 terminates the S1 applicationthat is not associated with the user equipment 71 though it is a part ofthe procedures toward the Home-eNB 72-2 and towards the MME 73 a. Whenthe HeNBGW 74 is deployed, the procedure that is not associated with theuser equipment 71 is communicated between the Home-eNB 72-2 and theHeNBGW 74 and between the HeNBGW 74 and the MME 73 a. The X2 interfaceis not set between the HeNBGW 74 and another node. The HeNBGW 74recognizes the execution of paging optimization as an option.

An example of a cell search method in a communication system will bedescribed next. FIG. 12 is a flowchart showing an outline from a cellsearch to an idle state operation performed by a user equipment (UE) inthe LTE communication system. When starting a cell search, in StepST1201, the user equipment synchronizes the slot timing and frame timingby a primary synchronization signal (P-SS) and a secondarysynchronization signal (S-SS) transmitted from a neighbor base station.

The P-SS and S-SS are collectively referred to as a synchronizationsignal (SS). Synchronization codes, which individually correspond tophysical cell identities (PCIs) assigned per cell, are assigned to thesynchronization signal (SS). The number of PCIs is currently studied in504 ways. These 504 ways are used for synchronization, and the PCIs ofthe synchronized cells are detected (specified).

In Step ST1202, next, the user equipment detects a cell-specificreference signal (CRS) being a reference signal (RS) transmitted fromthe base station per cell and measures the reference signal receivedpower (RSRP). The codes individually corresponding to the PCIs are usedfor the reference signal RS. Separation from another cell is enabled bycorrelation using the code. The code for RS of the cell is derived fromthe PCI specified in Step ST1201, which makes it possible to detect theRS and measure the RS received power.

In Step ST1203, next, the user equipment selects the cell having thebest RS reception quality, for example, cell having the highest RSreceived power, that is, best cell, from one or more cells that havebeen detected up to Step ST1202.

In Step ST1204, next, the user equipment receives the PBCH of the bestcell and obtains the BCCH that is the broadcast information. A masterinformation block (MIB) containing the cell configuration information ismapped to the BCCH over the PBCH. Accordingly, the MIB is obtained byobtaining the BCCH through reception of the PBCH. Examples of the MIBinformation include the downlink (DL) system bandwidth (also referred toas transmission bandwidth configuration (dl-bandwidth)), transmissionantenna number, and system frame number (SFN).

In Step ST1205, next, the user equipment receives the DL-SCH of the cellbased on the cell configuration information of the MIB, to therebyobtain a system information block (SIB) 1 of the broadcast informationBCCH. The SIB1 contains the information about the access to the cell,information on cell selection, and scheduling information about otherSIB (SIBk; k is an integer equal to or larger than two). In addition,the SIB1 contains a tracking area code (TAC).

In Step ST1206, next, the user equipment compares the TAC of the SIB1received in Step ST1205 with the TAC portion of a tracking area identity(TAI) in the tracking area list that has been already possessed by theuser equipment. The tracking area list is also referred to as a TAIlist. TAI is the identity of a tracking area and is formed of a mobilecountry code (MCC), a mobile network code (MNC), and a tracking areacode (TAC). MCC is a country code. MNC is a network code. TAC is thecode number of a tracking area.

In a case where the TAC received in Step ST1205 is identical to the TACincluded in the tracking area list as a result of the comparison of StepST1206, the user equipment enters an idle state operation in the cell.In a case where the TAC received in Step ST1205 is not included in thetracking area list as a result of the comparison, the user equipmentrequires a core network (EPC) including MME and the like to change atracking area through the cell for performing tracking area update(TAU).

The core network updates the tracking area list based on anidentification number (such as a UE-ID) of the user equipmenttransmitted from the user equipment with a TAU request signal. The corenetwork transmits the updated tracking area list to the user equipment.The user equipment rewrites (updates) the TAC list of the user equipmentbased on the received tracking area list. After that, the user equipmententers the idle state operation in the cell.

In the LTE, LTE-A, and universal mobile telecommunication system (UMTS),the introduction of a closed subscriber group (CSG) cell is studied. Asdescribed above, access is allowed for only one or a plurality of userequipments registered with the CSG cell. A CSG cell and one or aplurality of user equipments registered with the CSG cell constitute oneCSG. A specific identification number referred to as CSG-ID is added tothe thus constituted CSG. One CSG may contain a plurality of CSG cells.After being registered with any one of the CSG cells, the user equipmentcan access another CSG cell of the CSG to which the registered CSG cellbelongs.

Alternatively, the Home-eNB in the LTE and LTE-A and the Home-NB in theUMTS are used as the CSG cell in some cases. The user equipmentregistered with the CSG cell has a whitelist. Specifically, thewhitelist is stored in the subscriber identity module (SIM) or USIM. Thewhitelist stores the CSG information of the CSG cell with which the userequipment has been registered. Specific examples of the CSG informationmay include CSG-ID, tracking area identity (TAI), and TAC. Any one ofthe CSG-ID and TAC is adequate as long as they are associated with eachother. Alternatively, ECGI is adequate as long as the CSG-ID and TAC areassociated with ECGI.

As can be seen from the above, the user equipment that does not have awhitelist (including a case where the whitelist is empty in the presentinvention) is not allowed to access the CSG cell but is allowed toaccess the non-CSG cell only. On the other hand, the user equipmentwhich has a whitelist is allowed to access the CSG cell of the CSG-IDwith which registration has been performed as well as the non-CSG cell.

The HeNB and HNB are required to support various services. For example,in a certain service, an operator causes the predetermined HeNB and HNBto register user equipments therein and permits only the registered userequipments to access the cells of the HeNB and HNB, which increasesradio resources available for the user equipments and enables high-speedcommunication. The operator correspondingly sets a high charge comparedwith a normal service.

In order to achieve the above-mentioned service, the closed subscribergroup (CSG) cell accessible only to the registered (subscribed ormember) user equipments is introduced. It is required to install a largenumber of closed subscriber group (CSG) cells in shopping malls,apartment buildings, schools, companies, and the like. For example, thefollowing manner of use is required: the CSG cells are installed foreach store in shopping malls, for each room in apartment buildings, foreach classroom in schools, and for each section in companies such thatonly the users who have registered with the respective CSG cells arepermitted to use those CSG cells.

The HeNB/HNB is required not only to complement the communicationoutside the coverage of the macro cell (area complementing HeNB/HNB) butalso to support various services as described above (service providingHeNB/HNB). This also leads to a case where the HeNB/HNB is installedwithin the coverage of the macro cell.

The problem to be solved in the first embodiment will now be describedagain. It is disclosed that an NCT is associated with a legacy carrier(see Non-Patent Document 11). It is not disclosed, however, that withwhat legacy carrier an NCT is associated. This leads to a problem thatcommunication systems of Release 11 and the following releases, in whichlegacy carriers and NCTs coexist, cannot be operated normally andefficiently.

A solution in the first embodiment will be described below. An NCT isassociated with a legacy carrier belonging to the same frequency band asthat of the NCT. It is conceivable that a UE includes a wireless unitper frequency band. In this embodiment, as described above, the legacycarrier that has been associated (hereinafter, also referred to as“associated legacy carrier (abbreviated as ALC)”) and the NCT belong tothe same frequency band. Thus, the UE is merely required to operate awireless unit for one frequency band to receive an associated legacycarrier and an NCT. This reduces the power consumption of a UE. Thelegacy carrier may serve as the serving cell for the UE. The UE thatsupports an LTE is capable of transmission and reception in a legacycarrier equivalent to one serving cell.

Here, the legacy carrier is equivalent to a first carrier. The NCT isequivalent to a second carrier. The associated legacy carrier isequivalent to an associated carrier.

The following four (1) to (4) will be disclosed as specific examples ofthe association method in the first embodiment.

(1) The carrier that notifies a UE of the configuration of the NCT is acarrier associated with the NCT. One of the carriers that notify a UE ofthe configuration of the NCT may be the carrier associated with the NCT.In the specific example (1), the associated legacy carrier at the samefrequency band as that of the NCT notifies the UE of the configurationof the NCT. Here, the configuration of the NCT refers to the informationrequired for a UE to transmit and receive an NCT. The associated legacycarrier may notify the UE of the system information of the NCT, in placeof the configuration of the NCT. The configuration of the NCT and thesystem information of the NCT are information related to the NCT being asecond carrier, which is equivalent to carrier information.

(2) The carrier that notifies a UE of the PDSCH scheduling of an NCT isa carrier associated with the NCT. One carrier that notifies a UE of thePDSCH scheduling of an NCT may be a carrier associated with the NCT. Inthe specific example (2), the associated legacy carrier at the samefrequency band as that of the NCT notifies the UE of the PDSCHscheduling of the NCT.

(3) The carrier that is synchronized with an NCT is a carrier associatedwith the NCT. In more detail, a carrier that is synchronized with an NCTin time and frequency to such an extent that the UE does not needseparate synchronization processes is the carrier associated with theNCT. One of the carriers that are synchronized with an NCT may be acarrier associated with the NCT.

(4) Combination of (1) to (3).

3GPP is studying a synchronized NCT and a non-synchronized NCT. Thesynchronized NCT refers to an NCT that is synchronized with a legacycarrier in time and frequency to such an extent that the UE being areceiver does not need separate synchronization processes. Thenon-synchronized NCT refers to an NCT that is not synchronized with alegacy carrier in time and frequency with accuracy comparable to that ofa synchronized NCT (see 3GPP RAN1 #67 meeting report (hereinafter,referred to as “Non-Patent Document 12”).

The non-synchronized NCT may be associated with any legacy carrier in anon-limited manner, whereas the synchronized NCT may be associated withthe legacy carrier belonging to the same frequency band as that of theNCT. The non-synchronized NCT is not associated with a legacy carrier intime and frequency. It is therefore conceivable that even if the legacycarriers to be associated with a non-synchronized NCT are limited, thenumber of hardware blocks that need to be powered on separately from ahardware block for receiving a legacy carrier in the configuration of aUE device (implement) may increase compared with the case where asynchronized NCT is used. For this reason, it is preferable to limit thelegacy carriers to be associated with a synchronized NCT, whicheffectively reduce the power consumption of the UE, and not to limit thenon-synchronized NCTs. This allows for the construction of a flexiblecommunication system in that legacy carriers to be associated with anon-synchronized NCT are not limited.

FIG. 13 shows the concept of the solution in the first embodiment of thepresent invention. In FIG. 13, the horizontal axis indicates a frequencyf. Hereinafter, a legacy carrier may be referred to as “LC.” In theexample shown in FIG. 13, a legacy carrier (LC) 1 and an NCT1 belong toa frequency band A (band A). A legacy carrier (LC) 2, a legacy carrier(LC) 3, and an NCT2 belong to a frequency band B (band B).

For example, the legacy carrier to be associated with the NCT2 belongsto the same frequency band B as that of the NCT2. Legacy carriersbelonging to the same frequency band B as that of the NCT2 include thelegacy carrier (LC) 2 and the legacy carrier (LC) 3. The NCT2 isaccordingly associated with the legacy carrier (LC) 2 and the legacycarrier (LC) 3. The legacy carrier (LC) 1 belongs to the frequency bandA different from the frequency band B to which the NCT2 belongs. TheNCT2 is accordingly not associated with the legacy carrier (LC) 1.

The architecture of an NCT has not been disclosed in the discussion of3GPP. This embodiment will disclose the following two (1) and (2) asspecific examples of the architecture suitable for an NCT.

(1) The entity that configures an NCT is an entity that has the mediumaccess control (MAC) for hybrid automatic repeat request (HARQ), thatis, HARQ-MAC function, and the physical layer (PHY) function. The entitythat configures an NCT may also be referred to as an “NCT point” below.

(2) The NCT point is an entity that has the physical layer (PHY)function. The physical layer may have the HARQ-MAC function.

The NCT point is an entity that does not have the radio resource control(RRC) and MAC functions. The NCT point may use the packet dataconvergence protocol (PDCP), RRC, and MAC functions.

The associated legacy carrier may differ per UE. In that case, theassociated legacy carrier of each UE may be responsible for the PDCP,RRC, and MAC functions for each UE. In the case where the associatedlegacy carrier is an SCell, a PCell may be responsible for the PDCP,RRC, and MAC functions.

The base station may determine whether to operate a carrier to beconfigured as a legacy carrier or as an NCT. The operation as the legacycarrier and the operation as the NCT may switchable.

FIG. 14 shows the architecture of an NCT of the specific example (1). AnNCT point 1401 has a HARQ-MAC 1402 and a PHY 1403.

FIG. 15 shows the architecture of an existing cell (see Chapter 6.4 ofNon-Patent Document 1). An existing cell 1501 is an entity that has thefunctions of an RRC1502, a MAC1503, a HARQ-MAC1504, and a PHY1505. Evenif the cell is configured as a SCell for one UE1, it may be a PCell fora UE2 different from the UE1. Thus, even the cell being a SCell for theUE1 has the RRC and MAC functions. The architecture of an NCT and thearchitecture of an existing cell differ from each other in this respect.The existing cell is equivalent to the first cell and the cell of theNCT is equivalent to the second cell.

The architecture of an NCT, disclosed in the first embodiment, does nothave the RRC and MAC functions. This prevents a communication systemfrom becoming complicated in enabling the entity of the NCT.

The first embodiment above can achieve the following effects. The firstembodiment has disclosed the legacy carrier to be associated with anNCT, allowing for unified and normal operation of the communicationsystems of Release 11 and the following releases, in which legacycarriers and NCTs coexist.

It is conceivable that a UE may have a wireless unit per frequency band.According to the first embodiment, an associated legacy carrier and anNCT belong to the same frequency band, and thus, the UE is merelyrequired to operate a wireless unit for one frequency band for receivingthe associated legacy carrier and the NCT. Therefore, the powerconsumption of the UE can be reduced.

First Modification of First Embodiment

A first modification of the first embodiment will disclose anothersolution to the problem of the first embodiment described above. Thesolution in the first modification of the first embodiment will bedescribed below. This modification will mainly describe the partdifferent from the solution in the first embodiment described above andwill not describe the part similar to the first embodiment.

In this modification, an NCT is associated with a legacy carrier whosetiming advance group (TAG) is the same as that of the NCT.

In the case where the timing advance (TA) applied to the NCT expires ora timer expires in the UE, the UE may transmit the RACH in uplinkcarrier to be linked with an associated legacy carrier. Alternatively,the UE may transmit a random access preamble. The UE may receive, as aresponse to the RACH, a new TA value using an associated legacy carrier.The UE may receive a random access response in the associated legacycarrier and receive a new TA value.

The UE may employ the TA value received in an associated legacy carrierfor the NCT. This employment is enabled by associating an NCT with alegacy carrier whose timing advance group is the same as that of theNCT. This eliminates the need for RACH transmission in an uplink carrierfor link with the NCT. That is, it is not necessary to configure anuplink carrier for link with an NCT for RACH transmission alone. Thisimproves frequency use efficiency.

A timing advance (TA) is provided for compensating for an uplinkpropagation delay. The transmission from UEs are respectivelycompensated for by the UEs so as to align with the receiver window ofthe base station. The TA is a parameter used for instructing the UE fromthe base station to advance or delay the timings of transmission to thebase station (see Chapter 5.2.7.3 of Non-Patent Document 1).

The timing advance group (TAG) is a set of cells sharing the same TAvalue (see R1-120424 (hereinafter, referred to as “Non-Patent Document13”) by 3GPP). The TAG is configured by base stations (see Non-PatentDocument 13).

The UE receives timing advance in a random access process. To bespecific, the UE receives a timing advance (TA) over a random accessresponse being a response to a random access preamble.

Legacy carriers to be associated with a non-synchronized NCT may not belimited, whereas the synchronized NCT may be associated with a legacycarrier belonging to the same timing advance group as that of the NCT.The non-synchronized NCT is not synchronized with a legacy carrier intime and frequency, and thus, it is conceivable that even if the legacycarriers to be associated with a non-synchronized NCT are limited, alegacy carrier whose timing advance group is the same as that of the NCTis unlikely to exist. Thus, the legacy carriers to be associated with asynchronized NCT that conceivably includes a legacy carrier whose timingadvance group is the same as that of the NCT are preferably limited,whereas the legacy carriers to be associated with the non-synchronizedNCT are preferably not limited. This allows for the construction of aflexible communication system in that legacy carriers to be associatedwith a non-synchronized NCT are not limited.

The first modification of the first embodiment can be used incombination with the first embodiment described above.

The first modification of the first embodiment above can achieve thefollowing effect. As in the first embodiment, this modification hasdisclosed a legacy carrier to be associated with an NCT as in the firstembodiment, allowing for a unified and normal operation of thecommunication systems of Release 11 and the following releases, in whichlegacy carriers and NCTs coexist.

This modification also achieves the effect that the RACH transmission inan uplink carrier to be linked with an NCT is not required. That is,such an effect is achieved that an uplink carrier to be linked with anNCT for only transmitting the RACH is not required. This improvesfrequency use efficiency.

Second Modification of First Embodiment

The problem to be solved in a second modification of the firstembodiment will be described. It is disclosed that an NCT can beassociated with a legacy carrier (see Non-Patent Document 11). However,it is not disclosed, for example, when they are determined to beassociated. Thus, the communication systems of Release 11 and thefollowing releases, in which legacy carriers and NCTs coexist, cannot beoperated normally and efficiently.

The solution in the second modification of the first embodiment will bedescribed below. In the case where an NCT point is installed, a legacycarrier to be associated with the NCT, namely, an associated legacycarrier for the NCT is determined. The associated legacy carrier for theNCT may be determined when the operation of the NCT point is started. Itmay be determined that the associated legacy carrier cannot be changedduring the operation of the NCT point. The methods described in, forexample, the first embodiment and the first modification of the firstembodiment may be used as the method of determining an associated legacycarrier for an NCT.

In the traditional techniques, system information is stored by the RRCfunction. As disclosed in the first embodiment, in the case where theNCT point being an entity that configures an NCT has no RRC function,the NCT point cannot use the traditional methods to store the systeminformation of the own device.

The method of storing the configuration of an NCT or the systeminformation of an NCT will now be disclosed. The RRC of the legacycarrier to be associated with an NCT stores the system information ofthe NCT. This limits the entities that store the system information ofan NCT more than the method of storing the system information of an NCTaccording to a third modification of the first embodiment, describedbelow, preventing a communication system from becoming complicated. Acommunication system can be therefore constructed easily.

Next, the following three (1) to (3) will be disclosed as specificexamples of the method of notifying a UE of the configuration or systeminformation of an NCT.

(1) Notification is made through UE dedicated signaling. In more detail,notification is made from an associated legacy carrier to a UE throughUE dedicated signaling. Notification may be made from an associatedlegacy carrier to a UE in the RRC_CONNECTED state with the associatedlegacy carrier through dedicated signaling. In the case where the numberof the UEs that use an NCT is limited, the method (1) does not need torepeatedly made notification compared with the method (2) describedbelow, allowing for effective use of radio resources.

(2) Notification is made through broadcast signaling. More specifically,an associated legacy carrier notifies a UE being served thereby throughbroadcast signaling. Notification may be made using the MIB or SIB.Unlike the method (1), the method (2) does not need to establishdedicated signaling, and thus can effectively use radio resources in thecase where a large number of UEs use an NCT or in the case where a largenumber of UEs need to know the configuration of the NCT.

(3) Combination of the method (1) and the method (2). That is, thenotification method through UE dedicated signaling and the notificationmethod through broadcast signaling are used in combination. The method(3) will now be described.

The RAN1 69 meeting report by 3GPP (hereinafter, referred to as“Non-Patent Document 14”) discloses the co-channel deployment of an NCT.A specific example of the co-channel deployment will be described withreference to FIG. 16. FIG. 16 shows the concept of the co-channeldeployment of an NCT. The NCT has a bandwidth 1601, and the legacycarrier (LC) has a bandwidth 1602. The legacy carrier (LC) that isassociated, namely, an associated legacy carrier (ALC) may have thebandwidth 1602. The carrier frequency of the NCT is identical to thecarrier frequency of the legacy carrier (LC).

A specific example of the combination of the method (3) will now bedescribed below. The method (2) may be employed as the method ofnotifying the configuration of the NCT in the case where the NCTundergoes co-channel deployment, whereas the method (1) may be used asthe method of notifying the configuration of the NCT in the case wherethe NCT does not undergo co-channel deployment. In a specific example ofthe case where the NCT does not undergo co-channel deployment, thecarrier frequency of an NCT may differ from the carrier frequency of alegacy carrier or an associated legacy carrier.

A specific example of the method of notifying the configuration or thesystem information of an NCT that undergoes co-channel deployment willbe disclosed below. Only a parameter different from a legacy carrier oran associated legacy carrier is notified as the parameter of an NCT.

In the case where the configuration of an NCT is notified, the UE mayrecognize that the configuration that is not notified is identical tothe configuration of the legacy carrier or the associated legacycarrier. In the case where the system information of the NCT isnotified, the UE may recognize that the system information that is notnotified is identical to the system information of the legacy carrier orthe associated legacy carrier.

Specific examples of the parameters having different values between theNCT and the legacy carrier include bandwidths. Specific examples of theparameter having the same value between the NCT and the legacy carrierinclude carrier frequencies.

Next, the following twelve (1) to (12) will be disclosed as specificexamples of the parameters to be notified the UE as the configuration orthe system information of the NCT. Differences from the systeminformation in the traditional technique will be mainly described (seeNon-Patent Document 2).

(1) A parameter for differentiating between a legacy carrier and an NCT,which is, for example, a parameter indicating a legacy carrier or anNCT. Addition of this parameter enables the UE that has received thisparameter to differentiate between the operation for a legacy carrierand the operation for an NCT. The specific example (1) will be furtherdescribed below.

3GPP is studying to reduce cell-specific reference signals (CRSs) of anNCT more than legacy carriers (see Non-Patent Document 11). The CRS hasbeen traditionally used in measurement by the UE. The UE cannotaccordingly perform accurate measurement if it cannot recognize that ameasurement target is a legacy carrier or an NCT, leading to a problemof an inaccurate measurement in, for example, the comparison of thereception qualities between a legacy carrier and an NCT.

Addition of a parameter in the specific example (1) leads to such aneffect that in the case where the NCT is a measurement target, the UEcan employ a measurement method different from the traditionalmeasurement method to accurately compare the reception qualities betweenthe legacy carrier and the NCT. Specific examples of the measurementmethod different from a traditional measurement method include themethod that involves changing how to take an average depending on thenumber of CRS s.

The parameter of the specific example (1) may be an indication that themeasurement target is not an NCT or an indication that the measurementtarget is an NCT. In the specific example (1), it suffices to add aparameter to only the system information of the NCT newly added, and itis not necessary to add a parameter to the system information of alegacy carrier. In this respect, a communication system having excellentbackward compatibility can be constructed.

(2) A cell identity of an NCT, which is, for example, PCI, CGI, or ECGI.

(3) Information on which cell a measurement target is associated with.For example, the information on an associated legacy carrier. Specificexamples may include the carrier frequency of an associated legacycarrier and the cell identity of an associated legacy carrier. Thespecific example (3) will be further described below.

3GPP is studying to reduce P-SSs and S-SSs (see R1-121231 (hereinafter,referred to as “Non-Patent Document 15”) by 3GPP). The P-SSs and S-SSshave been traditionally used by the UE in cell search. Thus, if theP-SSs and the S-SS are reduced by an NCT, the UE will have difficulty incell search for the NCT in the traditional method.

As a result of the addition of the parameter of the specific example(3), the UE can obtain the information on an associated legacy carrierfor the NCT to perform cell search for the NCT via the associated legacycarrier. As a specific example of the cell search for the NCT via anassociated legacy carrier, for a synchronized NCT, for example, a frameboundary of the associated legacy carrier is conceivably employed.Specific examples of the employment may include configuring the frameboundary of the associated legacy carrier to be identical to the frameboundary of the NCT and providing an offset.

(4) A carrier frequency of an NCT. In the case of the specific example(4), the UE is not required to search for the carrier frequency of anNCT, reducing the time required for cell search by the UE. This reducesthe power consumption of the UE and reduces a processing load.

(5) A bandwidth of an NCT.

(6) A method of transmitting reference signals (RSs) or method oftransmitting measurement target signals. Specific examples include thenumber of transmissions of RSs in subframes and the bandwidth at which aCRS is transmitted. As described above, 3GPP is studying to reduce CRSsin the NCT more than the legacy carriers (see Non-Patent Document 11).As a result of the addition of parameters in the specific example (6),the UE can use the measurement method different from a traditionalmeasurement method in the case where an NCT is a measurement target tocompare the reception qualities between the legacy carrier and the NCT.Specific examples of the measurement method different from a traditionalmeasurement method may include changing how to take an average dependingon the number of CRSs.

(7) An index of an NCT. The index of an NCT may be associated with theidentity of the NCT or with the carrier frequency of the NCT. Thefollowing two (7-1) and (7-2) will be disclosed as specific examples ofthe method of adding the index of an NCT.

(7-1) Indexes are added to the NCTs associated with an associated legacycarrier. Specifically, indexes are added so as not to coincide with eachother between the NCTs associated with an associated legacy carrier. Asa result, the transmission and reception of indexes of NCTs allows theUE and the network to identify the NCT associated with an associatedlegacy carrier. Serial numbers are added as indexes. Specifically,serial numbers are provided for NCTs together with the associated legacycarrier. Alternatively, serial numbers are provided for the NCTsexcluding an associated legacy carrier.

(7-2) Indexes are added to the NCTs to be notified the UE. Specifically,indexes are added so as not to coincide with each other between the NCTsto be notified the UE. As a result, the transmission and reception ofindexes of the NCTs allows the UE and the network to identify the NCT tobe notified the UE. Alternatively, indexes may be added so as not tocoincide with each other between the NCT to be notified the UE and theSCell.

Serial numbers are added as indexes. Specifically, they are the serialnumbers for the NCTs to be notified a UE or the serial numbers for theNCTs to be notified the UE and the SCell. Serial numbers are provided tothe NCTs and the SCell, allowing for the use of SCellIndex of thetraditional technique (see Chapter 6.3.4 of Non-Patent Document 2).

The specific example (7-2) can use a traditional technique, preventing acommunication system from becoming complicated. In the specific example(7-2), a parameter indicating a legacy carrier or an NCT to SCellIndexof the traditional technique. The parameter of the specific example(7-2) may be an indication that the carrier is not an NCT, or anindication that the carrier is an NCT.

(8) Location information of the place in which an NCT point isinstalled. The use of the parameter of the specific example (8) allowsthe network to obtain the location information on the NCT via the UE. Inthe case where the parameter of the specific example (8) is used, forexample, the eNB requests the location information on the NCT point fromthe UE. The UE that has received the request receives the parameter“location information on the place in which an NCT point is installed,”and notifies the eNB of the location information on the place in whichthe NCT point is installed. In the case where the NCT point isconfigured by a movable entity, a great advantage is achieved byallowing the network to obtain the location information on an NCT viathe UE without using communication such as communication between basestations. This is because the communication such as communicationbetween base stations is not required every time an entity moves.Specific examples of the movable entity configuring an NCT point includea HeNB, a movable RN, and a movable RRH.

(9) Information indicating synchronization or non-synchronization. Inthe case of synchronization, a legacy carrier to be synchronized may benotified. The use of the parameter of the specific example (9) allowsthe UE to recognize the method of detecting an NCT, the method oftracking an NCT, the method of measuring an NCT, and other method.

(10) Uplink information on an NCT. Specific examples of the uplinkinformation include a carrier frequency of an uplink carrier for linkwith an NCT, a bandwidth, and a parameter for differentiating between alegacy carrier and an NCT. If the uplink information on an NCT issimilar to that of the uplink of an associated legacy carrier, theinformation indicating the similarity is sufficient.

(11) Information on a TAG to which an NCT belongs. In the case where theperiod of TA applied to an NCT expires or a timer expires, the UE maytransmit a RACH in an uplink carrier for link with the legacy carrierbelonging to the same TAG. Alternatively, the UE may transmit a randomaccess preamble. The UE may newly receive a TA value as a response tothe RACH, using the legacy carrier. The UE may receive a random accessresponse in the legacy carrier and then receive a new TA value. The UEmay employ the TA value received in the legacy carrier for an NCT. Thisemployment is enabled by the UE recognizing the TAG to which an NCTbelongs and recognizing the legacy carrier whose TAG is the same as thatof the UE. This eliminates the need for transmitting a RACH in an uplinkcarrier for link with an NCT. That is, it is not necessary to configurean uplink carrier for link with an NCT for only transmitting a RACH.This improves frequency utilization efficiency.

(12) Combination of (1) to (11) above.

As an example, the parameter for differentiating between a legacycarrier and an NCT in the specific example (1) and the information onwhich cell a carrier is associated with in the specific example (3) canbe notified in combination to achieve the following effect. 3GPP isstudying to reduce cell-specific reference signals (CRS s) in an NCTmore than a legacy carrier (see Non-Patent Document 11). The CRS hastraditionally been used by a UE in measurement. For example, in the casewhere a measurement target is an NCT, the UE can employ the measurementresults of the associated legacy carrier.

As another example, the information on which cell a carrier isassociated with in the specific example (3), the carrier frequency of anNCT in the specific example (4), and the information indicatingsynchronization or non-synchronization in the specific example (9) canbe notified in combination to achieve the following effect. The cellsearch of an NCT via an associated legacy carrier can be performed morereliably. As a specific example of the cell search of an NCT via anassociated legacy carrier for a synchronized NCT, it is conceivable toemploy, for example, a frame boundary of the associated legacy carrier.For example, 3GPP has proposed that a UE should be notified of an NCTcarrier but has not disclosed, for example, a combination of parametersas described in this modification (R2-122180 (hereinafter, referred toas “Non-Patent Document 22”) by 3GPP). Therefore, an associated legacycarrier is unclear and it is difficult to judge whether or not the NCTis synchronized from the description disclosed in Non-Patent Document22. This does not allow the UE to accurately perform cell search of anNCT via an associated legacy carrier.

As another example, the method of transmitting RSs in the specificexample (6) and the bandwidth of an NCT in the specific example (5) canbe notified in combination to achieve the following effects. The UE canrecognize the bandwidth of an NCT and the bandwidth at which an RS istransmitted by a specific method of transmitting an RS, therebyrecognizing, for example, a ratio between the bandwidth at which an RSis transmitted and the bandwidth of an NCT. This allows the UE toaccurately estimate a radio environment. For example, 3GPP has proposedthat the RS configuration should be notified but has not disclosed, forexample, the combination of parameters as described in this modification(see Non-Patent Document 19). Thus, for example, the ratio between thebandwidth at which an RS is transmitted and the bandwidth of an NCTcannot be recognized from the description detailed in Non-PatentDocument 19.

The combination of the parameters of the specific examples (1) to (11)is not limited to the examples described above. Notification of thecombination of the parameters of (1) to (11) above allows for moreefficient operation of the communication systems of Release 11 and thefollowing releases, in which legacy carriers and NCTs coexist.

Specific examples of the entity that configures an NCT for the UE willnow be described. The associated legacy carrier configures an NCT forthe UE. The configuration for the UE may be performed per UE, for a UEbeing served, or for a UE being served in an RRC_CONNECTED state.

The following four (1) to (4) will be disclosed as specific examples ofthe entity that configures an NCT for the UE particularly in the casewhere an associated legacy carrier is configured as the SCell in CA.

(1) The PCell judges whether or not to configure an NCT for the UE. Whenconfiguring an NCT, the PCell requests the associated legacy carrierbeing an SCell to configure an NCT. The associated legacy carrier beingan SCell configures an NCT for the UE. The PCell judges whether or notto configure an NCT for the UE, so that a data throughput or the like asthe entire communication system using a PCell, an SCell, and an NCTassociated with an SCell for the UE can be readily taken intoconsideration.

(2) The PCell judges whether or not to configure an NCT for the UE. Whenconfiguring an NCT, the PCell configures an NCT for the UE. The PCellmay configure an SCell (SCell Configuration) and may also configure anNCT. The configuration area of the NCT may be added to the existingsignaling for SCell configuration.

In the case where the configuration area of an NCT is added to theexisting signaling for SCell configuration, signaling does not need tobe newly added for NCT configuration, preventing the communicationsystem from becoming complicated. Specific examples of the existingsignaling for SCell configuration include“radioResourceConfigDedicatedSCell” and “PhysicalConfigDedicatedSCell”(see Non-Patent Document 2).

In the specific example (2), the PCell configures an NCT, andaccordingly, the PCell alone configures a carrier for the UE, such asconfiguring an SCell and configuring an NCT. This reduces the processingload of the UE. In the specific example (2), the PCell judges whether ornot to configure an NCT as in the specific example (1), achieving aneffect similar to that of the specific example (1).

(3) The SCell being an associated legacy carrier judges whether or notto configure an NCT for the UE. When configuring an NCT, the SCellconfigures an NCT for the UE. The SCell being an associated legacycarrier judges whether or not to configure an NCT, so that theprocessing load, the radio environment, or the like of the associatedlegacy carrier can be readily taken into consideration.

(4) The SCell being an associated legacy carrier judges whether or notto configure an NCT for the UE. When configuring an NCT, the SCellrequests the PCell to configure an NCT. The PCell configures an NCT forthe UE. The PCell may configure an NCT for the UE using the existingsignaling for SCell configuration. The configuration area of an NCT maybe added to the existing signaling for SCell configuration.

In the case where the configuration area of an NCT is added to theexisting signaling for SCell configuration, signaling does not need tobe newly added for the configuration of an NCT, preventing thecommunication system from becoming complicated. Specific examples of theexisting signaling for SCell configuration include“radioResourceConfigDedicatedSCell” and “Physic alConfigDedicatedSCell”(see Non-Patent Document 2).

In the specific example (4), the PCell configures an NCT for the UE, andaccordingly, the PCell alone configures a carrier for the UE, such asconfiguring an SCell and configuring an NCT. This leads to an effectthat the processing load of the UE can be reduced. In the specificexample (4), the SCell judges whether or not to configure an NCT as inthe specific example (3), achieving an effect similar to that of thespecific example (3).

FIG. 17 shows an example sequence in the case where the specific example(1) is used as the entity that configures an NCT for the UE in thecommunication system according to the second modification of the firstembodiment of the present invention. The sequence shown in FIG. 17 isthe sequence in the case where an associated legacy carrier isconfigured as the SCell in CA.

In Step ST1701, the PCell configures an SCell (hereinafter, merelyreferred to as “SCell”) being an associated legacy carrier (ALC) for theUE.

In Step ST1702, the PCell judges whether or not to configure an NCTassociated with the SCell. The PCell moves to Step ST1703 when judgingto configure an NCT in Step ST1702 or repeats the process of Step ST1702when judging not to configure an NCT in Step ST1702.

In Step ST1703, the PCell requests the SCell to configure an NCT. InStep

ST1703, the PCell may notify the SCell of the identity of the UE being aconfiguration target in addition to requesting the SCell to configure anNCT.

In Step ST1704, the SCell, which has received a request to configure anNCT transmitted from the PCell in Step ST1703, judges whether or not theNCT can be configured. In this judgment, the SCell may take intoconsideration the processing load of the own cell, radio environment, orthe like. The SCell moves to Step ST1705 when judging that an NCT cannotbe configured in Step ST1704 or moves to Step ST1706 when judging thatan NCT can be configured in Step ST1704.

In Step ST1705, the SCell notifies the PCell that an NCT cannot beconfigured. Specifically, the SCell transmits “Nack” to the PCell.

In Step ST1706, the SCell notifies the PCell that an NCT can beconfigured. Specifically, the SCell transmits “Ack” to the PCell.

When judging that an NCT can be configured in Step ST1704, in StepST1707, the SCell notifies the UE of the configuration of the NCT.

In Step ST1708, the PCell judges whether it has received, from theSCell, “Ack” as a response to the request to configure an NCT. The PCellmoves to Step ST1709 when judging that it has received “Ack” in StepST1708 or moves to Step ST1710 when judging that it has not received“Ack” in Step ST1708.

In Step ST1709, the PCell recognizes that an NCT has been configured forthe UE.

In Step ST1710, the PCell recognizes that an NCT has not been configuredfor the UE, that is, an NCT has not been configured.

FIG. 18 shows an example sequence in the case where the specific example(2) is used as the entity that configures an NCT for the UE in thecommunication system according to the second modification of the firstembodiment of the present invention. The sequence shown in FIG. 18 isthe sequence in the case where an associated legacy carrier isconfigured as the SCell in CA. The sequence shown in FIG. 18 is similarto the sequence shown in FIG. 17, and thus, the same steps will bedenoted by the same step numbers and common description will be omitted.

In the specific example (2), when judging to configure an NCT associatedwith an SCell in Step ST1702, the PCell moves to Step ST1801. In StepST1801, the PCell inquires the configuration of the NCT from the SCell.In Step ST1801, the PCell may notify the SCell of the identity of the UEbeing a configuration target in addition to inquiring the configurationof the NCT.

In the specific example (2), when judging that an NCT can be configuredin Step ST1704, the SCell moves to Step ST1802. In Step ST1802, theSCell notifies the PCell that the NCT can be configured. Specifically,the SCell transmits “Ack” to the PCell. In this case, the SCell being anassociated legacy carrier (ALC) may notify the PCell of theconfiguration of the NCT. It may not be necessary to notify theconfiguration of the NCT if the PCell is the entity that stores theconfiguration of the NCT.

After the process of Step ST1802, the SCell moves to Step ST1804. InStep ST1804, the SCell recognizes that the NCT has been configured forthe UE.

In the specific example (2), when judging that an NCT cannot beconfigured in Step ST1704, the SCell performs the process of Step ST1705and then moves to Step ST1803. In Step ST1803, the SCell recognizes thatthe NCT has not been configured for the UE, that is, the NCT has notbeen configured.

In Step ST1805, the PCell judges whether or not to have received “Ack”from the SCell as a response to the inquiry about the configuration ofthe NCT. The PCell moves to Step ST1806 when judging to have received“Ack” in Step ST1805 or ends the process when judging to not havereceived “Ack” in Step ST1805.

In Step ST1806, the PCell notifies the UE of the configuration of theNCT. In the case the SCell notifies the PCell of the configuration ofthe NCT in Step ST1802, the PCell may perform the configuration of theNCT, which has been received from the SCell in Step ST1802, for the UEin Step ST1806.

FIG. 19 shows an example sequence in the case where the specific example(2) is used as the entity that configures an NCT for the UE in thecommunication system according to the second modification of the firstembodiment of the present invention. The sequence shown in FIG. 19 isthe sequence in the case where an associated legacy carrier isconfigured as the SCell in CA. FIG. 19 shows the sequence in the case ofconfiguring an NCT in addition to configuring an SCell in the specificexample (2) of the entity that configures an NCT for the UE. Thesequence shown in FIG. 19 is similar to the sequences shown in FIGS. 17and 18, and thus, the same steps will be denoted by the same stepnumbers and common description will be omitted.

In the example shown in FIG. 19, the PCell makes judgment in Step ST1702before configuring an SCell being an associated legacy carrier (ALC).After that, the communication system performs the following processes ofSteps ST1801 to ST1804.

When judging to have received “Ack” in Step ST1805, in Step ST1901, thePCell configures an SCell as well as configuring an NCT for the UE. ThePCell may notify the configuration of the SCell including theconfiguration of an NCT. In the case where the SCell notifies the PCellof the configuration of an NCT in Step ST1802, the PCell may perform theconfiguration of an NCT received from the SCell in Step ST1802 for theUE in the Step ST1901.

FIG. 20 shows an example sequence in the case where the specific example(3) is used as the entity that configures an NCT for the UE in thecommunication system according to the second modification of the firstembodiment of the present invention. The sequence shown in FIG. 20 isthe sequence in the case where an associated legacy carrier isconfigured as the SCell in CA. The sequence shown in FIG. 20 is similarto the sequence shown in FIG. 17, and thus, the same steps will bedenoted by the same step numbers and common description will be omitted.

In the example shown in FIG. 20, after the process of Step ST1701, inStep ST2001, the SCell judges whether or not to configure an NCT. TheSCell moves to Step ST2002 when judging to configure an NCT in StepST2001 or repeats the process of Step ST2001 when judging not toconfigure an NCT in Step ST2001.

In Step ST2002, the SCell reports to the PCell that it will configure anNCT. Specifically, the SCell transmits to the PCell the reportindicating the configuration of an NCT, which is the informationindicating that the SCell will configure an NCT. In the reportindicating the configuration of an NCT, the SCell may also notify thePCell of the identity of the UE for which an NCT has been configured,the system information of the configured NCT, or the like.

In Step ST2003, the PCell that has received the report indicating theconfiguration of an NCT in Step ST2002 recognizes that an NCT has beenconfigured for the UE.

When judging to configure an NCT in Step ST2001, in Step ST2004, theSCell notifies the UE of the configuration of an NCT.

FIG. 21 shows an example sequence in the case where the specific example(4) is used as the entity that configures an NCT for the UE in thecommunication system according to the second modification of the firstembodiment of the present invention. The sequence shown in FIG. 21 isthe sequence in the case where an associated legacy carrier isconfigured as the SCell in CA. The sequence shown in FIG. 21 is similarto the sequences shown in FIGS. 17 and 20, and thus, the same steps willbe denoted by the same step numbers and common description will beomitted.

In the example shown in FIG. 21, when judging to configure an NCT inStep ST2001, the SCell moves to Step ST2101. In Step ST2101, the SCellrequests the PCell to configure an NCT. At this time the SCell being anassociated legacy carrier (ALC) may notify the PCell of the identity ofthe UE being a configuration target and the configuration of an NCT. Ifthe PCell is the entity that stores the configuration of the NCT, it maynot be necessary to notify the configuration of an NCT.

When judging to configure an NCT in Step ST2001, the SCell recognizesthat an NCT has been configured for the UE in Step ST2102.

In Step ST2103, the PCell, which has received the request to configurean NCT in Step ST2101, notifies the UE being a target for which an NCTis configured in the request to configure an NCT (hereinafter, alsoreferred to as an “NCT configuration target”) that an NCT will beconfigured. In the case where the configuration of an NCT is notifiedthe PCell from the SCell together with the request to configure an NCTin Step ST2101, in Step ST2103, the PCell may perform the configurationof the NCT received from the SCell in Step ST2101 for the UE being anNCT configuration target for the request to configure an NCT receivedfrom the SCell in Step ST2101.

The second modification of the first embodiment may be used incombination with the first embodiment or the first modification of thefirst embodiment described above.

The second modification of the first embodiment described above canachieve the following effects. This modification has disclosed when anassociated legacy carrier is determined, allowing the communicationsystems of Release 11 and the following releases in which legacycarriers and NCTs coexist to be operated uniformly and normally.

In this modification, the information indicating whether or not there isan NCT that takes, as an associated legacy carrier, an SCell to benotified the UE from the PCell may be added to the configuration of theSCell (SCell configuration). Alternatively, the configuration of an NCTdisclosed in the second modification of the first embodiment may beadded.

This achieves such an effect that the UE that has received theconfiguration of the SCell can operate differently for the legacycarrier associated with an NCT and the legacy carrier not associatedwith an NCT.

Third Modification of First Embodiment

The third modification of the first embodiment will disclose anothersolution to the problem in the second modification of the firstembodiment. The solution in the third modification of the firstembodiment will be described below. Differences from the solution in thesecond modification of the first embodiment will be mainly described.The parts that will not be described below are similar to those of thesecond modification of the first embodiment.

In the third modification of the first embodiment, not limited to thecase where an NCT point is determined, an associated legacy carrier forthe NCT is determined in a semi-static or dynamic manner. Alternatively,the associated legacy carrier during the operation of the NCT point ismade changeable. As the method of determining an associated legacycarrier for an NCT, which is an initial value, the methods described in,for example, the first embodiment and the first modification of thefirst embodiment may be used. Specific examples in which an initialvalue is set include the case where an NCT point is configured and thecase where an NCT point starts operating.

The following two (1) and (2) will be disclosed as the specific examplesof the range in which an associated legacy carrier for an NCT isdetermined in a semi-static or dynamic manner.

(1) The associated legacy carrier for an NCT is determined per UE. Theassociated legacy carrier for the NCT may differ from UE to UE thattransmits and receives data using the NCT.

(2) The associated legacy carrier for an NCT is determined per NCT. Theassociated legacy carrier for the NCT is the same between the UEs thattransmit and receive data using the NCT.

The following three (1) to (3) will be disclosed as specific examples ofthe method of determining an associated legacy carrier for an NCT in asemi-static or dynamic manner.

(1) The associated legacy carrier for an NCT is determined depending onthe radio environment of an associated legacy carrier. It is conceivablethat the radio environment of an associated legacy carrier may changedepending on the location of a UE. Thus, the determination method of thespecific example (1) is highly compatible with the specific example (1)of the range in which the associated legacy carrier for an NCT isdetermined in a semi-static or dynamic manner.

(2) The associated legacy carrier for an NCT is determined depending onthe load status of an associated legacy carrier. It is conceivable thatthe load status of an associated legacy carrier does not change per UE.Thus, the determination method of the specific example (2) is highlycompatible with the specific example (2) of the range in which theassociated legacy carrier for an NCT is determined in a semi-static ordynamic manner described above.

(3) Combination of the determination method of the specific example (1)and the determination method of the specific example (2).

Specific description will be given of the determination method dependingon the radio environment of an associated legacy carrier, which is thespecific example (1) of the method of determining an associated legacycarrier for an NCT in a semi-static or dynamic manner. The associatedlegacy carrier for an NCT is determined per UE depending on the radioenvironment of an associated legacy carrier. The radio environment of anassociated legacy carrier differs depending on the location of a UE.Therefore, determining the associated legacy carrier for an NCT per UEallows a legacy carrier optimum for each UE to be configured as theassociated legacy carrier for an NCT.

The associated legacy carrier judges whether or not to change anassociated legacy carrier based on the UE measurement results. Thefollowing two (1) and (2) will be disclosed as specific examples of thejudgment.

(1) For the reception quality of an associated legacy carrier lower thana predetermined threshold, the associated legacy carrier is changed.Contrastingly, for the reception quality of an associated legacy carrierequal to or higher than a predetermined threshold, the associated legacycarrier is not changed.

(2) In the presence of a legacy carrier having a reception qualitybetter than that of an associated legacy carrier, the associated legacycarrier is changed. Contrastingly, in the absence of a legacy carrierhaving a reception quality better than that of an associated legacycarrier, the associated legacy carrier is not changed.

The associated legacy carrier determines a new associated legacy carrier(hereinafter, also referred to as a “target legacy carrier”) based onthe UE measurement results. Hereinafter, an associated legacy carrierbefore change may be referred to as a “source legacy carrier.” Aspecific example of the method of determining a target legacy carrierwill be disclosed below. The legacy carrier having the best receptionquality is taken as a target legacy carrier.

The source legacy carrier may notify the target legacy carrier of arequest indicating that the target legacy carrier will serve as anassociated legacy carrier for a target NCT (hereinafter, also referredto as an “associated legacy carrier change (ALC) request). At that time,the source legacy carrier may notify the target legacy carrier of theconfiguration of the NCT, specifically, the information required for theUE to receive an NCT or the system information of an NCT. A specificexample of the system information of an NCT is similar to that of thesecond modification of the first embodiment, which will not be describedhere.

In the notification of an associated legacy carrier change request, theexisting signaling “Handover Request” (see TS 36.423 V11.1.0(hereinafter, referred to as “Non-Patent Document 16”) by 3GPP) or“Handover Required” (see Chapter 8.4.1 of TS 36.413 V11.0.0(hereinafter, referred to as “Non-Patent Document 17”) 3GPP) may beused. “Handover Request” is notified the target eNB from the source eNBby means of an X2 interface. “Handover Required” is notified the MMEfrom the source eNB by means of an S1 interface.

The method of notifying an associated legacy carrier change requestdescribed above may be used not only in the case where the source legacycarrier and the target legacy carrier are configured in different eNB sbut also in the case where the source legacy carrier and the targetlegacy carrier are configured in the same eNB. This allows the methodsof notifying an associated legacy carrier change request to be unifiedirrespective of the configuration of the eNB, preventing thecommunication system from becoming complicated.

In the case where an associated legacy carrier change request isnotified by means of an S1 interface, a notification may be made in theorder of the source legacy carrier, the MME that controls the sourcelegacy carrier, the MME that controls the target legacy carrier, and thetarget legacy carrier.

In this case, the existing signaling may be provided with an indicatorindicating an “associated legacy carrier change request.” In addition,an area of the system information of an NCT may be added to the existingsignaling. This eliminates the need for adding new signaling, allowingfor easy construction of a communication system. Further, acommunication system having excellent backward compatibility can beconstructed.

The target legacy carrier that has received an associated legacy carrierchange request may judge whether or not to serve as the associatedlegacy carrier for the NCT. The target legacy carrier may judge whetheror not to serve as the associated legacy carrier for the NCT inconsideration of the processing load of the legacy carrier.

The target legacy carrier may notify the source legacy carrier of thejudgment results on whether or not to serve as the associated legacycarrier for the NCT. In such a case, the target legacy carrier maynotify the source legacy carrier of the configuration of the NCT, forexample, the information required for a UE to receive a target legacycarrier or the system information of a target legacy carrier.

In the notification of the judgment results on whether or not the targetlegacy carrier will serve as the associated legacy carrier for the NCT,the existing signaling “Handover Request Acknowledge” (see Chapter 8.2.1of Non-Patent Document 16) or “Handover Command” (see Chapter 8.4.1 ofNon-Patent Document 17) may be used. “Handover Request Acknowledge” maybe notified the source eNB from the target eNB by means of an X2interface. “Handover Command” is notified the MME from the target eNB bymeans of an S1 interface.

The method of notifying the judgment results on whether or not thetarget legacy carrier serves as the associated legacy carrier for an NCTmay be used not only in the case where the source legacy carrier and thetarget legacy carrier are configured in different eNBs but also in thecase where the source legacy carrier and the target legacy carrier areconfigured in the same eNB. This allows the methods of notifying thejudgment results on whether or not the target legacy carrier serves asthe associated legacy carrier for an NCT to be unified irrespective ofthe configuration of an eNB, preventing a communication system frombecoming complicated.

In the case where the judgment results on whether or not the targetlegacy carrier serves as the associated legacy carrier for an NCT arenotified by means of an S1 interface, a notification may be made in theorder of the target legacy carrier, the MME that controls the targetlegacy carrier, the MME that controls the source legacy carrier, and thesource legacy carrier.

In this case, the existing signaling may be provided with the indicatorindicating the “judgment results on whether or not the target legacycarrier serves as the associated legacy carrier for an NCT.” Thiseliminates the need for adding new signaling, allowing for easyconstruction of a communication system. Further, a communication systemhaving excellent backward compatibility can be constructed.

The source legacy carrier notifies a target UE that it will change theassociated legacy carrier. At that time, the source legacy carrier maynotify the target UE of the system information of the target legacycarrier, which has been received from the target legacy carrier. In thiscase, when an associated legacy carrier is changed, the UE does not needto obtain the system information of the target legacy carrier from thetarget legacy carrier, allowing the associated legacy carrier to bechanged smoothly.

The existing signaling “RRCConnectionReconfiguration message” or“mobilityControlInformation” (see Chapter 1.2.1 of Non-PatentDocument 1) may be used to notify that an associated legacy carrier willbe changed. “RRCConnectionReconfiguration message” and“mobilityControlInformation” are notified the UE from the source eNB.

The above-mentioned method of notifying an indication that an associatedlegacy carrier will be changed may be used not only in the case wherethe source legacy carrier and the target legacy carrier are configuredin different eNBs but also in the case where the source legacy carrierand the target legacy carrier are configured in the same eNB. Thisallows the methods of notifying that an associated legacy carrier willbe changed to be unified irrespective of the configuration of an eNB,preventing a communication system from becoming complicated.

In the case where the existing signaling is used to notify that anassociated legacy carrier will be changed, the existing signaling may beprovided with an indicator indicating that “an associated legacy carrierwill be changed.” This eliminates the need for adding new signaling,allowing for easy construction of a communication system. Further, acommunication system having excellent backward compatibility can beconstructed.

The source legacy carrier notifies a target NCT that it will change anassociated legacy carrier. At that time, the source legacy carrier maynotify a target NCT of the system information of the target legacycarrier, which has been received from the target legacy carrier.

The UE, which has been notified that an associated legacy carrier willbe changed, changes the associated legacy carrier for the target NCT.When changing an associated legacy carrier, the UE may use the systeminformation of the target legacy carrier received from the source legacycarrier. The following two (1) and (2) will be disclosed as specificexamples of changing a legacy carrier.

(1) The legacy carrier, which is monitored for receiving the schedulingof the PDSCH of the target NCT, is changed from the source legacycarrier to the target legacy carrier.

(2) The carrier, which is synchronized with a target NCT, is changedfrom the source legacy carrier to the target legacy carrier.

As the method of determining an associated legacy carrier, thenon-synchronized NCT may use the method of determining an associatedlegacy carrier according to the radio environment of the associatedlegacy carrier, which is the specific example (1) of the method ofdetermining an associated legacy carrier in a semi-static or dynamicmanner. As the method of determining an associated legacy carrier, thesynchronized NCT may avoid using the method of determining an associatedlegacy carrier according to the radio environment of the associatedlegacy carrier, which is the specific example (1) of the method ofdetermining an associated legacy carrier in a semi-static or dynamicmanner.

The synchronized NCT and its associated legacy carrier are conceivablysimilar to each other in the radio environment for the UE. Thus, in thecase where an associated legacy carrier is to be changed due to a poorradio environment of the associated legacy carrier, the radioenvironment of the NCT per se may become poor, leading to a fear thatthe communication with the UE using an NCT may not be allowed. Thus, fora synchronized NCT, the use of the method of determining an associatedlegacy carrier according to the radio environment of the associatedlegacy carrier in the specific example (1) may be avoided as the methodof determining an associated legacy carrier, as described above.

In contrast, it is conceivable that a non-synchronized NCT and itsassociated legacy carrier are not necessarily similar to each other inthe radio environment for the UE. Thus, even in the case where anassociated legacy carrier is to be changed due to a poor radioenvironment of the associated legacy carrier, the communication with theUE using an NCT may be allowed. Thus, for a non-synchronized NCT, themethod of determining an associated legacy carrier according to theradio environment of the associated legacy carrier may be used as themethod of determining an associated legacy carrier, as described above.

Description will now be given of the method of determining a legacycarrier to be associated with the NCT according to the load status of anassociated legacy carrier, which is the specific example (2) of themethod of determining an associated legacy carrier in a semi-staticmanner or dynamic manner described above. Examples of the load statusinclude the load status of a MAC, the load status of an RRC, and theload status of scheduling.

The associated legacy carrier judges whether or not to change anassociated legacy carrier based on a load status. A specific example ofthe judgment will be disclosed below. In the case where the load of theassociated legacy carrier is higher than a predetermined threshold, theassociated legacy carrier is changed. In the case where the load of anassociated legacy carrier is the same as or lower than a predeterminedthreshold, the associated legacy carrier is not changed.

The associated legacy carrier determines a target carrier being a newassociated legacy carrier based on the load status of a neighbor legacycarrier. The following two (1) and (2) will be disclosed as specificexamples of the method of determining a target legacy carrier.

(1) A target legacy carrier is selected from legacy carriers that can beassociated with an NCT.

(2) A legacy carrier with the lowest load status is taken as the targetlegacy carrier.

The following two (1) and (2) will be disclosed as specific examples ofthe method of obtaining the load status of a legacy carrier in theneighborhood of the source legacy carrier being an associated legacycarrier before change.

(1) The source legacy carrier requests a neighbor base station or aneighbor legacy carrier to report its load status. Alternatively, whenjudging to change an associated legacy carrier, the source legacycarrier may request to report a load status. The source legacy carriernotifies the request to report a load status, thereby requesting areport of a load status. The neighbor base station or the neighborlegacy carrier that has received the request to report a load statusreports the load status to the source legacy carrier.

“Resource Status Request” (see Chapter 8.3.6.2 of Non-Patent Document16) that is notified by means of an X2 interface being the existingsignaling may be used in the notification of the request to report aload status. “Resource Status Request” is notified by means of an X2interface. In the use of “Resource Status Request,” the existingsignaling may be provided with an indicator that requests the “loadstatus,” for example, the “load status of a MAC,” the “load status of anRRC,” or the “load status of scheduling.” This eliminates the need foradding new signaling, allowing for easy construction of a communicationsystem. Further, a communication system having excellent backwardcompatibility can be constructed.

“Resource Status Response” (see Chapter 8.3.6.2 of Non-Patent Document16) being the existing signaling may be used in the notification of thereport of a load status. “Resource Status Response” may be notified bymeans of an X2 interface. In the use of “Resource Status Response,” theexisting signaling may be provided with the “load status,” for example,the “load status of a MAC,” the “load status of an RRC,” or the “loadstatus of scheduling.” This eliminates the need for adding newsignaling, allowing for easy construction of a communication system.Further, a communication system having excellent backward compatibilitycan be constructed.

(2) The base station or legacy carrier reports the load status to aneighbor base station or legacy carrier. The base station may report theload status periodically. “Resource Status Response” (see Chapter8.3.6.2 of Non-Patent Document 16) being the existing signaling may beused in the notification of a report of a load status. “Resource StatusResponse” is notified by means of an X2 interface.

In the use of “Resource Status Response,” the existing signaling may beprovided with the indicator requesting the “load status,” for example,the “load status of a MAC,” the “load status of an RRC,” or the “loadstatus of scheduling.” In such a case, a change is made such that theexisting signaling can transmit “Resource Status Response” withoutreceiving “Resource Status Request.” This eliminates the need for addingnew signaling, allowing for easy construction of a communication system.Further, a communication system having excellent backward compatibilitycan be constructed.

The processes after a new associated legacy carrier is determined can beperformed as in the method of determining an associated legacy carrieraccording to the radio environment of the associated legacy carrier,which is the specific example (1) of the method of determining anassociated legacy carrier in a semi-static or dynamic manner asdescribed above. Thus, description thereof will not be given.

FIG. 22 shows an example sequence in the case where the specific example(1) of the method of determining an associated legacy carrier in asemi-static or dynamic manner in the communication system according tothe third modification of the first embodiment of the present invention.

In Step ST2201, the UE notifies the source legacy carrier, being theassociated legacy carrier before change, of a measurement report.

In Step ST2202, the source legacy carrier judges whether or not tochange the associated legacy carrier (ALC) based on the measurementreport received in Step ST2201. As a specific example, the source legacycarrier judges whether or not the reception quality of the source legacycarrier received in Step ST2201 is lower than a predetermined threshold,to thereby judge whether or not to change the associated legacy carrier(ALC).

When judging that the received reception quality of the source legacycarrier is lower than the predetermined threshold, the source legacycarrier judges to change the associated legacy carrier (ALC) and thenmoves to Step ST2203. When judging that the received reception qualityof the source legacy carrier is equal to or higher than thepredetermined threshold, the source legacy carrier judges not to changethe associated legacy carrier (ALC) and then repeats the judgment ofStep ST2202.

In Step ST2203, the source legacy carrier notifies the UE of themeasurement configuration required to determine a target legacy carrier.

The UE that has received the measurement configuration in Step ST2203performs measurement according to the received measurementconfiguration. In Step ST2204, the UE notifies the source legacy carrierof the measurement report reporting the measurement results.

Upon receipt of the measurement report in Step ST2204, in Step ST2205,the source legacy carrier determines a target legacy carrier based onthe measurement report received in Step ST2204.

In Step ST2206, the source legacy carrier notifies the target legacycarrier of an associated legacy carrier (ALC) change request being amessage requesting the target legacy carrier to serve as the associatedlegacy carrier for the target NCT. At that time, the source legacycarrier may notify the target legacy carrier of the system informationof an NCT. The ALC change request is notified using, for example,“Handover Request” being the existing signaling.

In Step ST2207, the target legacy carrier that has received the ALCchange request in Step ST2206 judges whether or not to serve as anassociated legacy carrier (ALC). The target legacy carrier moves to StepST2208 when judging to serve as an associated legacy carrier or moves toStep ST2209 when judging not to serve as an associated legacy carrier.

In Step ST2208, the target legacy carrier notifies the source legacycarrier that it will serve as an associated legacy carrier, as thejudgment results on whether or not it will serve as the associatedlegacy carrier for the target NCT. Specifically, the target legacycarrier notifies that it will serve as an associated legacy carrier bytransmitting “Ack” as a response to the ALC change request. The targetlegacy carrier may transmit “Ack” using, for example, “Handover RequestAcknowledge” being the existing signaling. When notifying that it willserve as an associated legacy carrier, the target legacy carrier maynotify the source legacy carrier of the system information of a targetlegacy carrier.

In Step ST2209, the target legacy carrier notifies the source legacycarrier that it will not serve as an associated legacy carrier, as thejudgment results on whether or not it will serve as the associatedlegacy carrier for the target NCT. Specifically, the target legacycarrier notifies that it will not serve as an associated legacy carrierby transmitting “Nack” as a response to the ALC change request. Thetarget legacy carrier may transmit “Nack” using, for example, “HandoverRequest Acknowledge” being the existing signaling.

In Step ST2210, the source legacy carrier judges whether or not it hasreceived, from the target legacy carrier, the notification indicatingthat the target legacy carrier will serve as an associated legacycarrier, as the judgment results on whether or not the target legacycarrier will serve as the associated legacy carrier for a target NCT.Specifically, the source legacy carrier judges whether or not it hasreceived “Ack” from the target legacy carrier.

When judging that it has received “Ack” from the target legacy carrier,the source legacy carrier judges that it has received, from the targetlegacy carrier, the notification indicating that the target legacycarrier will serve as an associated legacy carrier and then moves toStep ST2211. When judging that it has not received “Ack” from the targetlegacy carrier, namely, when judging that it has received “Nack,” thesource legacy carrier judges that it has been notified that the targetlegacy carrier will not serve as an associated legacy carrier and thenmoves to Step ST2213.

In Step ST2211, the source legacy carrier notifies the UE that it willchange an associated legacy carrier. The source legacy carrier notifiesthat it will change the associated legacy carrier using, for example,“RRCConnectionReconfiguration message” or “mobilityControlInformation”being the existing signaling. When receiving the system information ofthe target legacy carrier from the target legacy carrier in Step ST2208,in Step ST2211, the source legacy carrier notifies a target UE of thesystem information of the target legacy carrier received in Step ST2208as well as notifying that it will change an associated legacy carrier.

In Step ST2212, the source legacy carrier notifies the target NCT thatit will change an associated legacy carrier.

In Step ST2213, the source legacy carrier determines a target legacycarrier again. At that time, the source legacy carrier may select atarget legacy carrier from the legacy carriers other than the legacycarrier that has notified in Step ST2209 that it will not serve as theassociated legacy carrier for a target NCT. The source legacy carriermay again notify the UE of the measurement configuration required todetermine a target legacy carrier.

In Step ST2214, the UE changes the associated legacy carrier for thetarget NCT from the source legacy carrier to the target legacy carrier.In changing, the UE may use the system information of the target legacycarrier received in Step ST2211.

FIG. 23 shows an example sequence in the case where the specific example(2) of the method of determining an associated legacy carrier in asemi-static or dynamic manner in the communication system according tothe third modification of the first embodiment of the present invention.The sequence shown in FIG. 23 is similar to the sequence shown in FIG.22, and thus, the same steps will be denoted by the same step numbersand common description will be omitted.

In Step ST2301, the source legacy carrier judges whether or not tochange an associated legacy carrier. In the example shown in FIG. 23,the source legacy carrier judges whether or not the load of the owncarrier being an associated legacy carrier is higher than apredetermined threshold, to thereby judge whether or not to change theassociated legacy carrier.

When judging that the load of the own carrier is higher than thepredetermined threshold, the source legacy carrier judges to change theassociated legacy carrier and then moves to Step ST2302. When judgingthat the load of the own carrier is equal to or lower than thepredetermined threshold, the source legacy carrier judges not to changethe associated legacy carrier and then repeats the judgment of StepST2301.

For example, when judging that the MAC load of the own carrier is higherthan a predetermined threshold, the source legacy carrier judges tochange the associated legacy carrier and then moves to Step ST2302. Whenjudging that the MAC load of the own carrier is equal to or lower thanthe predetermined threshold, the source legacy carrier judges not tochange the associated legacy carrier and then repeats the judgment ofStep ST2301.

In Step ST2302, the source legacy carrier transmits a request forreporting a load status to neighbor legacy carriers, to thereby requestto report the load status. The neighbor legacy carriers include a legacycarrier that will be selected later as a target legacy carrier. Therequest for reporting a load status is transmitted using “ResourceStatus Request” being the existing signaling.

In Step ST2303, the neighbor legacy carriers that have received therequest for reporting a load status in Step ST2302 transmit the reportof the load status to the source legacy carrier. The neighbor legacycarriers include the legacy carrier that will be selected later as atarget legacy carrier. The report of the load status is transmittedusing, for example, “Resource Status Response” being the existingsignaling.

In Step ST2304, the source legacy carrier determines a target legacycarrier based on the load statuses of the neighbor legacy carriersreceived in Step ST2303.

The third modification of the first embodiment can achieve the followingeffect in addition to the effects similar to those of the secondmodification of the first embodiment. This modification enables moredynamic operation than the second modification of the first embodiment.

Disclosed next is the case where the PCell is changed when the NCT isconfigured for the UE and a legacy carrier to be associated with the NCTis the PCell. Herein, the PCell is not limited to the PCell in the casewhere CA is configured for the UE and refers to the cell in which the UEis connected to a higher layer.

The PCell (also referred to as a “target PCell”) after change judgeswhether or not to configure an NCT for a target UE.

For example, the PCell (also referred to as a “source PCell”) beforechange transmits, to the target PCell, a message requesting the targetPCell to change the PCell for the UE (hereinafter, also referred to as a“PCell change request message”). When receiving the PCell change requestmessage of the UE, the target PCell may judge whether or not toconfigure an NCT for the target UE.

The PCell change request message may include the system information ofthe NCT configured before the PCell is changed, as well as theinformation indicating a request to change the PCell. Alternatively, thePCell change request message may apply the method of notifying anassociated legacy carrier change request to be notified the targetlegacy carrier from the source legacy carrier, which has been disclosedin this modification.

The target PCell judges whether or not to configure an NCT using thesystem information of the NCT received from the source PCell and, whenit judges to configure an NCT, determines the details of the systemconfiguration of the NCT.

The information on whether or not the reception quality of an NCT isgood, whether the reception quality of an NCT is higher or lower than apredetermined threshold, or whether or not the NCT can be continuouslyused may be used to judge whether or not to configure an NCT. Suchinformation may be created by the source PCell based on the measurementresults from the UE and may be notified the target PCell from the sourcePCell in advance. Such information may be notified with, for example, aPCell change request message.

The method disclosed in this modification may be applied in the casewhere the configuration of an NCT remains unchanged before and after thePCell is changed.

In the case where different NCTs are configured for a target UE beforeand after the PCell is changed, the target PCell notifies the sourcePCell of the system information of the configured NCT. Alternatively,the radio resource configuration configured by the target PCell may benotified. The radio resource configuration may include the systeminformation of the configured NCT. The method of using a “HO requestacknowledge” message disclosed in this modification may be applied asthe notification method.

The source PCell that has received the system information of a newlyconfigured NCT from the target PCell notifies the UE of thisinformation. When receiving the radio resource configuration includingthe system information of the NCT, the source PCell may notify thisinformation. The method of using, for example, an“RRCCconnectionreconfiguration” message or message control information(abbreviated as MCI), disclosed in this modification, may be applied asthe notification method.

The source PCell notifies the UE of the system information of the NCTreceived from the target PCell, allowing the UE to synchronize andcommunicate with the target PCell and the newly configured NCT.

The method disclosed herein is also applicable to the case where thePCell in the same eNB is changed and in the case where PCells indifferent eNBs are changed.

Also in the case where the NCT configuration remains unchanged beforeand after the PCell is changed, the method disclosed above isapplicable. This allows the system information of the NCT configured bya target PCell or the radio resource configuration including the systeminformation of the NCT to be reliably notified the source PCell and theUE, reducing disconnections due to a condition mismatch between the UEand the target PCell. “Disconnection” means that connection is cut off.

In the case where the target PCell determines not to configure an NCT,the target PCell may avoid notifying the source PCell of the systeminformation of an NCT. The target PCell may notify the message that doesnot contain the system information of the NCT but contains only theradio resource configuration of the target PCell. Similarly, the sourcePCell may avoid notifying the UE of the system information of the NCT.The source PCell may notify the message that does not contain the systeminformation of the NCT but contains only the radio resourceconfiguration of the target PCell. This allows the UE to recognize thatan NCT is not configured after the change of the PCell.

When configuring an NCT for a target UE, the target PCell being thePCell after change may perform CA for the UE. Alternatively, the legacycarrier to be associated with the NCT may be one of the SCellsconfigured in CA.

In this case, the method disclosed above may be applied, and further,the target PCell may notify the source PCell of the CA configurationafter the change of the PCell. Alternatively, the source PCell maynotify the UE of the CA configuration after the change of the PCell.Examples of the CA configuration include the configuration informationof one or a plurality of SCells for which CA is performed and the systeminformation. In addition, the information indicating which SCell servesas the associated legacy carrier for an NCT may be notified together.

This allows the UE to synchronize and communicate with the Scell andalso with the NCT.

The NCT may be configured as one SCell in CA. A similar method isapplicable also in this case.

The method disclosed above allows, in the case where an NCT isconfigured for the UE and the associated legacy carrier for the NCT is aPCell, the use of the NCT in changing the PCell without disconnectingthe communication before and after the PCell is changed, enablinghigh-speed communication between the UE and the network.

Second Embodiment

The problem to be solved in the second embodiment will be described.3GPP proposes that the scheduling of the PDSCH to be mapped to the NCTis notified the UE over the PDCCH of the legacy carrier. Notifying theUE of the scheduling of the PDSCH of the legacy carrier over the PDCCHof the legacy carrier is referred to as cross-carrier scheduling (seeR1-121466 (hereinafter, referred to as “Non-Patent Document 18”) by3GPP).

The legacy carrier that performs scheduling of the PDSCH to be mapped tothe NCT is the same as the legacy carrier that notifies the UE of thescheduling results of the PDSCH to be mapped to the NCT. This allows thescheduling and the notification of the scheduling results to beperformed in the same legacy carrier, preventing a control delay of thecommunication system. Such a legacy carrier is referred to as a“scheduling legacy carrier (abbreviated as SLC).”

Cross-carrier scheduling has been disclosed that notifies the UE of thescheduling of the PDSCH to be mapped to an SCell over the PDCCH of thePCell (see Chapter 11.1 of Non-Patent Document 1). However, thecross-carrier scheduling method suitable for an NCT has not beendisclosed.

For example, if the scheduling legacy carrier is configured to be in“deactivation,” unfortunately, cross-carrier scheduling to the NCT isnot allowed. This leads to a problem that the communication systems ofRelease 11 and the following releases, in which legacy carriers and NCTscoexist, cannot be operated normally and efficiently using cross-carrierscheduling.

Further, there is no disclosure of whether or not the UE that has beennotified of the configuration of an NCT or the system information of anNCT always needs to consider the NCT to be activated. In the case wherethe UE that has been notified of the configuration of an NCT or thesystem information of an NCT always considers the NCT to be activated,unfortunately, the power consumption of the UE will increase.

The solution in the second embodiment to the above-mentioned problemwill now be described. The UE that has been notified of theconfiguration of an NCT or the system information of an NCT does notalways need to consider the NCT to be activated. Specifically, the NCTwhose configuration or system information has been notified can becontrolled to be in “activation” or “deactivation” (hereinafter, alsocollectively referred to as “activation/deactivation”).

The following three (1) to (3) will be disclosed as specific examples ofthe cross-carrier scheduling method suitable for an NCT.

(1) For the scheduling legacy carrier, “deactivation” is prohibited. Or,the scheduling legacy carrier is always configured to be in“activation.” The activation/deactivation of an NCT is instructedexplicitly from the scheduling legacy carrier through signaling. Thescheduling legacy carrier is prohibited from “deactivation” or is alwaysconfigured to be in “activation,” always enabling cross-carrierscheduling from the scheduling legacy carrier to the NCT.

(2) When the scheduling legacy carrier is in “deactivation,” the NCT isalso in “deactivation.” Explicit instruction of “deactivation” of an NCTthrough signaling may be omitted. Upon receipt of the signalingindicating “deactivation” of a scheduling legacy carrier, the UErecognizes that the NCT will also be in “deactivation.” In the case ofthe specific example (2), the UE does not need the operation ofreceiving the signaling of “deactivation” of an NCT, reducing theprocessing load and power consumption of a UE. As a result, thescheduling legacy carrier will not be in “deactivation” during theactivation of the NCT. Therefore, the problem that cross-carrierscheduling to an NCT is not allowed in the case where the schedulinglegacy carrier is configured to be in “deactivation” can be solved.

(3) The shift of the activation/deactivation state is the same betweenthe scheduling legacy carrier and the NCT. The explicit instruction ofactivation/deactivation of an NCT through signaling may be omitted. Whenreceiving the signaling indicating activation/deactivation of ascheduling legacy carrier, the UE recognizes that the state of the NCTalso shits in the same manner. In the case of the specific example (3),the UE does not need the operation of receiving the signaling ofactivation/deactivation of an NCT, reducing the processing load andpower consumption of the UE. As a result, the scheduling legacy carrierwill not be in “deactivation” during the “activation” of the NCT.Therefore, in the case where the scheduling legacy carrier is configuredto be in “deactivation,” the problem that cross-carrier scheduling to anNCT is not allowed can be solved.

The scheduling legacy carrier may be the associated legacy carrier foran NCT. The scheduling legacy carrier may be a PCell or may not be aPCell. The scheduling legacy carrier may be an SCell.

The following three (1) to (3) will be disclosed as specific examples ofthe method of recognizing whether or not a target cell is a schedulinglegacy carrier by the entity that configures or determines theactivation/deactivation of a scheduling legacy carrier. In thisdescription, for convenience, the scheduling legacy carrier is an“associated legacy carrier,” the scheduling legacy carrier is an“SCell,” and the entity that configures or determines theactivation/deactivation of a scheduling legacy carrier is a “PCell.”

(1) In the case where an NCT associated with a target cell is present,that cell is recognized as an associated legacy carrier. The followingthree (1-1) to (1-3) will be disclosed as specific examples.

(1-1) In the case of the second modification of the first embodiment, anassociated legacy carrier is determined in a static manner. In the casewhere an NCT point is installed or in the case where an NCT point startsoperating, the target cell notifies a neighbor cell or base station thatit serves as an associated legacy carrier. For example, “X2 SETUPREQUEST” (see Chapter 9.1.2.3 of Non-Patent Document 16) to be notifiedby means of an X2 interface, which is the existing signaling, is used innotifying that the target cell serves as an associated legacy carrier.In that case, the information on whether or not there is an associatedNCT may be added to the “Served Cells” parameters. The systeminformation of an NCT described in the second modification of the firstembodiment may be added.

(1-2) In the case of the third modification of the first embodiment, anassociated legacy carrier is determined in a semi-static or dynamicmanner. The target cell that serves as an associated legacy carriernotifies a neighbor cell or base station that it serves as an associatedlegacy carrier. For example, “ENB CONFIGURATION UPDATE” (see Chapter9.1.2.8 of Non-Patent Document 16) to be notified by means of an X2interface, which is the existing signaling, is used in notifying thatthe target cell serves as an associated legacy carrier. In that case,the information on whether or not there is an associated NCT may beadded to the “Served Cells to Modify” parameters. Alternatively, thesystem information of an NCT described in the second modification of thefirst embodiment may be added.

(1-3) The entity that configures or determines theactivation/deactivation of a scheduling legacy carrier inquires a targetcell of whether or not the target cells include an associated NCT.Specifically, the entity transmits, to target cells, an inquiry ofwhether or not there is an associated NCT. The target cells that havereceived the inquiry respond to the inquiry of whether or not there isan associated NCT.

(2) In the case where the target cells include an associated NCT and oneor more UEs are notified of the configuration of the NCT, that cell isrecognized as an associated legacy carrier. The following two (2-1) and(2-2) will be disclosed as specific examples.

(2-1) In the case of notifying the UE of the configuration of an NCT orin the case of receiving the report that the configuration of the NCThas been notified, the entity that configures or determines theactivation/deactivation of a scheduling legacy carrier recognizes thatcell as an associated legacy carrier. For example, the entity thatconfigures or determines the activation/deactivation of a schedulinglegacy carrier, which is the PCell in FIGS. 17 to 21 described above,recognizes a target cell as a scheduling legacy carrier in Step ST1709of FIG. 17, Step ST1806 of FIG. 18, Step ST1901 of FIG. 19, Step ST2003of FIG. 20, and Step ST2101 of FIG. 21 that have disclosed in the secondmodification of the first embodiment.

(2-2) The entity that configures or determines theactivation/deactivation of a scheduling legacy carrier inquires a targetcell of whether there is an associated NCT and whether or not one ormore UEs have been notified of the configuration of the NCT.Specifically, the entity transmits, to a target cell, an inquiry ofwhether or not there is an associated NCT and whether or not one or moreUEs have been notified of the configuration of the NCT. The target cellthat has received the inquiry responds to the inquiry of whether or notthere is an associated NCT and whether or not the one or more UEs havebeen notified of the configuration of the NCT.

(3) In the case where a target cell is configured as a scheduling legacycarrier, that cell is recognized as an associated legacy carrier. Thatis, the entity that has configured a target cell as a scheduling legacycarrier configures or determines the activation/deactivation of thescheduling legacy carrier. This eliminates the “notification” or“inquiry,” unlike the specific examples (1) and (2), preventing acontrol delay of the communication system and reducing the processingload of the communication system.

In the case where the entity that configures or determines theactivation/deactivation of a scheduling legacy carrier will not orcannot recognize whether or not a target cell is a scheduling legacycarrier, the specific example (1) of the cross-carrier scheduling methodsuitable for an NCT, described above, is applicable. This prevents thetarget cell from “deactivation,” that is, causes the target cell to bealways in “activation” even if the target cell is a scheduling legacycarrier, always enabling cross-carrier scheduling from the target cellto the NCT.

FIG. 24 shows an example sequence in the case where the specific example(1) is used as the cross-carrier scheduling method suitable for an NCTin the communication system according to the second embodiment of thepresent invention. The example shown in FIG. 24 will be described withthe entity that configures or determines the activation/deactivation ofa scheduling legacy carrier being a PCell and the scheduling legacycarrier (SLC) being an SCell.

In Step ST2401, the PCell configures an SCell for the UE.

In Step ST2402, the PCell judges whether or not the SCell being a targetwhose activation/deactivation is configured or determined is ascheduling legacy carrier (SLC). When judging that the SCell is ascheduling legacy carrier, the PCell moves to Step ST2403. When thePCell judges that the SCell is not a scheduling legacy carrier,description will not be given because it is not specific to the idea ofthe present invention.

The specific example of the method of recognizing, by the entity thatconfigures or determines the activation/deactivation of a schedulinglegacy carrier, whether or not a target cell is a scheduling legacycarrier may be used as a specific method of judging, by the PCell,whether or not the SCell is a scheduling legacy carrier.

In Step ST2403, the PCell prohibits the SCell from “deactivation.”Specifically, the PCell manages the SCell such that it is prohibitedfrom “deactivation.” That is, the PCell always keeps the SCell in“activation.”

In Step ST2404, the PCell notifies the target UE that the SCell will beconfigured to be in “activation.”

In Step ST2405, the SCell configures an NCT for the UE. Here, the entitythat configures an NCT for the UE is not limited to the SCell, and thespecific examples of the entity that configures an NCT for the UE, whichhave been disclosed in the second modification of the first embodiment,may be used. The process of Step ST2405 can be performed, for example,prior to Step ST2401 without any problem.

In Step ST2406, the SCell performs scheduling of the PDSCH. The SCellmay perform scheduling of the PDSCH to be mapped to the NCT.

In Step ST2407, the SCell judges whether or not the PDSCH will be mappedto the NCT as the result of the scheduling of Step ST2406. When judgingthat the PDSCH will be mapped to the NCT, the SCell moves to StepST2408. When judging that the PDSCH will not be mapped to the NCT, theSCell moves to Step ST2410. Although the example in which theactivation/deactivation of an NCT is determined based on whether or notthe PDSCH is mapped to the NCT has been disclosed, theactivation/deactivation of an NCT may be determined based on othercriteria.

In Step ST2408, the SCell notifies the UE that an NCT is configured tobe in “activation.”

In Step ST2409, the SCell performs, for the UE, cross-carrier schedulingof the PDSCH to be mapped to the NCT.

In Step ST2410, the SCell notifies the UE that the NCT has beenconfigured to be in “deactivation.”

FIG. 25 shows an example sequence in the case where the specific example(2) is used as the cross-carrier scheduling method suitable for an NCTin the communication system according to the second embodiment of thepresent invention. The example shown in FIG. 25 will be described withthe entity that configures or determines the activation/deactivation ofa scheduling legacy carrier being a PCell and the scheduling legacycarrier (SLC) being an SCell. The sequence shown in FIG. 25 is similarto the sequence shown in FIG. 24, and thus, the same steps will bedenoted by the same step numbers and common description will be omitted.

In the example shown in FIG. 25, after the process of Step ST2401, inStep ST2501, the PCell performs scheduling of the PDSCH. The PCell mayperform scheduling of the PDSCH to be mapped to the SCell.

In Step ST2502, the PCell judges whether or not the PDSCH will be mappedto the SCell as the result of the scheduling of Step ST2501. Whenjudging that the PDSCH will be mapped to the SCell, the PCell moves toStep ST2503. When judging that the PDSCH will not be mapped to theSCell, the PCell moves to Step ST2506. Although the example in which theactivation/deactivation of an SCell is determined based on whether ornot the PDSCH will be mapped to the SCell has been disclosed here, theactivation/deactivation of an SCell may be determined based on othercriteria.

In Step ST2503, the PCell notifies the UE that it will configure theSCell to be in “activation”.

In Step ST2504, the PCell performs, for the UE, cross-carrier schedulingof the PDSCH to be mapped to the SCell.

In Step ST2505, the PCell notifies the SCell that it will configure theSCell to be in “activation.”

In Step ST2506, the PCell notifies the UE that it will configure theSCell to be in “deactivation.” In Step ST2507, the PCell notifies theSCell that it will configure the SCell to be in “deactivation.”

In Step ST2508, the SCell judges whether the own cell is configured tobe in “activation” or “deactivation.” The SCell may judge whether or notthe own cell is configured to be in “deactivation.” When judging thatthe own cell is not configured to be in “deactivation,” the SCell movesto Step ST2406. When judging that the own cell is configured to be in“deactivation,” the SCell moves to Step ST2509.

In Step ST2509, the SCell recognizes that the NCT is configured to beprohibited from “activation.” The SCell recognizes that the PDSCH isprohibited from being mapped to the NCT.

In Step ST2510, the UE judges whether or not the SCell is configured tobe in “activation” or “deactivation.” The UE may judge whether or notthe SCell is configured to be in “deactivation.” When judging that theSCell is configured to be in “deactivation,” the UE moves to StepST2511. When judging that the SCell is not configured to be in“deactivation,” the UE moves to Step ST2408.

In Step ST2511, the UE recognizes that the NCT is also configured to bein “deactivation.”

FIG. 26 shows an example sequence in the case where specific example (3)is used as the cross-carrier scheduling method suitable for an NCT inthe communication system according to the second embodiment of thepresent invention. The example shown in FIG. 26 will be described withthe entity that configures or determines the activation/deactivation ofa scheduling legacy carrier being a PCell and the scheduling legacycarrier (SLC) being an SCell. The sequence shown in FIG. 26 is similarto the sequences shown in FIGS. 24 and 25, and thus, the same steps willbe denoted by the same step numbers and common description will beomitted.

In the example shown in FIG. 26, after the processes of Step ST2401,Steps ST2501 to ST2507, and Step ST2405, in Step ST2601, the UE judgeswhether or not the SCell is configured to be in “activation” or“deactivation.” The UE may judge whether or not the SCell is configuredto be in “deactivation.” When judging that the SCell is configured to bein “deactivation,” the UE moves to Step ST2511. When judging that theSCell is not configured to be in “deactivation,” the UE moves to StepST2602.

In Step ST2602, the UE recognizes that the NCT is also configured to bein “activation.” The process of Step ST2511, which is performed by theUE in the case where the UE moves from Step ST2601 to Step ST2511, andthe processes of Steps ST2508, ST2509, ST2406, ST2407, and ST2409, whichare performed by the SCell after the process of Step ST2405, are similarto those of the sequences shown in FIGS. 24 and 25 described above.

The second embodiment described above can achieve the following effect.The communication systems of Release 11 and the following releases inwhich legacy carriers and NCTs coexist can be operated normally andefficiently using cross-carrier scheduling.

First Modification of Second Embodiment

The problem to be solved in a first modification of the secondembodiment will be described. There is no disclosure of thecross-carrier scheduling method suitable for an NCT in the case wherethe scheduling legacy carrier serves as an SCell. Therefore, thecommunication systems of Release 11 and the following releases in whichlegacy carriers and NCTs coexist cannot be operated normally andefficiently using cross-carrier scheduling.

The following two (1) and (2) will be disclosed as the solution in thefirst modification of the second embodiment.

(1) The PCell performs cross-carrier scheduling of the PDSCH to bemapped to the NCT.

(2) In the case where the PCell performs scheduling of the PDSCH to bemapped to the SCell using cross-carrier scheduling, the PCell performscross-carrier scheduling of the PDSCH to be mapped to the NCT. In thecase where scheduling of the PDSCH to be mapped to the SCell isperformed over the PDCCH of the SCell, the PCell or SCell performscross-carrier scheduling of the PDSCH to be mapped to the NCT.

In the two methods described above, in the case where the PCell performscross-carrier scheduling of the PDSCH to be mapped to the SCell, thePCell performs cross-carrier scheduling of the PDSCH to be mapped to theNCT. As a result, in the case where the PCell performs cross-carrierscheduling of the PDSCH to be mapped to the SCell, the UE is merelyrequired to receive the PDCCH of the PCell to receive the scheduling ofthe PDSCH to be mapped to the SCell and to receive the scheduling of thePDSCH to be mapped to the NCT. That is, the UE is not required toreceive the PDCCH of the SCell. This reduces the processing load of theUE.

FIG. 27 shows the concept of the solution (1) in the first modificationof the second embodiment of the present invention. In the solution (1),the scheduling of the PDSCH to be mapped to the NCT is notified over thePDCCH of the PCell. The UE receives the PDCCH of the PCell to receivethe scheduling of the PDSCH to be mapped to the NCT.

FIGS. 28 and 29 show the concept of the solution (2) in the firstmodification of the second embodiment of the present invention. FIG. 28shows the case where the scheduling of the PDSCH to be mapped to theSCell is performed by the PCell using cross-carrier scheduling. FIG. 29shows the case where the scheduling of the PDSCH to be mapped to theSCell is performed over the PDCCH of the SCell.

In the case where the scheduling of the PDSCH to be mapped to the SCellis performed by the PCell using cross-carrier scheduling in the solution(2), as shown in FIG. 29, the scheduling of the PDSCH to be mapped tothe NCT is notified over the PDCCH of the PCell. The UE receives thePDCCH of the PCell to receive the scheduling of the PDSCH to be mappedto the NCT.

In the case where the scheduling of the PDSCH to be mapped to the SCellis performed over the PDCCH of the SCell in the solution (2), as shownin FIG. 29, the scheduling of the PDSCH to be mapped to the NCT isnotified over the PDCCH of the PCell or the PDCCH of the SCell. The UEreceives the PDCCH of the PCell or the PDCCH of the SCell to receive thescheduling of the PDSCH to be mapped to the NCT.

The first modification of the second embodiment described above canachieve the following effect in addition to the effects similar to thoseof the second embodiment. In the case where the PCell performscross-carrier scheduling of the PDSCH to be mapped to the SCell, the UEis merely required to receive the PDCCH of the PCell to receive thescheduling of the PDSCH to be mapped to the SCell and to receive thescheduling of the PDSCH to be mapped to the NCT. That is, the UE is notrequired to receive the PDCCH of the SCell. This reduces the processingload of the UE.

Second Modification of Second Embodiment

The problem to be solved in a second modification of the secondembodiment will be described. In the case where the PCell performsscheduling of the PDSCH to be mapped to the SCell using the firstmodification of the first embodiment, the following problem may occur ifthe PCell performs the cross-carrier scheduling of the PDSCH to bemapped to the NCT. In such a case, the scheduling of the PDSCH to bemapped to the PCell, the PDSCH to be mapped to the SCell, and the PDSCHto be mapped to the NCT need to be notified over the PDCCH of the PCell.This may lead to a problem of insufficient resources for the PDCCH ofthe PCell.

The solution in the second modification of the second embodiment will bedisclosed below. The PCell is prohibited from performing cross-carrierscheduling of the PDSCH to be mapped to the SCell. The scheduling of thePDSCH to be mapped to the SCell is performed over the PDCCH of theSCell. The SCell performs cross-carrier scheduling of the PDSCH to bemapped to the NCT. The PCell may perform cross-carrier scheduling of thePDSCH to be mapped to the NCT.

FIG. 30 shows the concept of the solution in the second modification ofthe second embodiment of the present invention. In the solution of thesecond modification of the second embodiment, the scheduling of thePDSCH to be mapped to the SCell is notified over the PDCCH of the SCell.The cross-carrier scheduling over the PDCCH of the PCell is prohibited.FIG. 30 shows the prohibited cross-carrier scheduling by adding “x” tothe arrow.

The UE receives the PDCCH of the SCell to receive the scheduling of thePDSCH to be mapped to the SCell. The scheduling of the PDSCH to bemapped to the NCT is notified over the PDCCH of the SCell or over thePDCCH of the PCell. The UE receives the PDCCH of the SCell or the PDCCHof the PCell to receive the scheduling of the PDSCH to be mapped to theNCT.

The second modification of the second embodiment described above canachieve the following effect in addition to the effects similar to thoseof the second embodiment. The scheduling of the PDSCH to be mapped tothe PCell, the PDSCH to be mapped to the SCell, and the PDSCH to bemapped to the NCT, which are notified over the PDCCH of the PCell, isnot necessary. This can prevent the problem of insufficient resources ofthe PDCCH of the PCell.

Third Modification of Second Embodiment

The problem to be solved in a third modification of the secondembodiment will be described. 3GPP proposes the use of the enhancedcontrol channel (E-PDCCH) or cross-carrier scheduling to notify thescheduling of the PDSCH to be mapped to the NCT. In this proposal, whichof the E-PDCCH and the cross-carrier scheduling is used is configured bythe legacy carrier (see R1-122175 (hereinafter, referred to as“Non-Patent Document 19”) by 3GPP). However, Non-Patent Document 19 doesnot disclose how to select the E-PDCCH or the cross-carrier schedulingfor use to notify the scheduling of the PDSCH to be mapped to the NCT.Therefore, the communication systems of Release 11 and the followingreleases in which legacy carriers and NCTs coexist cannot be operatednormally and efficiently using cross-carrier scheduling.

The following two (1) and (2) will be disclosed as the solution in thethird modification of the second embodiment.

(1) In the case where there is an uplink for link to an NCT, the E-PDCCHis used to notify the scheduling of the PDSCH to be mapped to the NCT.

In the case where there is an uplink for link to an NCT, the responsesignal to the uplink data needs to be notified in downlink. The enhancedHARQ indicator channel (E-HICH) is studied as the method of notifying aresponse signal to the uplink data in a carrier to which the PDCCH isnot transmitted. It is also studied to separately configure channels,the E-HICH and the E-PDCCH, for the UE.

Therefore, in the case where there is an uplink for link to the NCT inwhich a response signal to the uplink data needs to be notified indownlink, the E-PDCCH highly compatible with the E-HICH is used toschedule the PDSCH to be mapped to the NCT. This prevents thecommunication system from becoming more complicated than the case wherethe method of transmitting a response signal to the uplink data is newlyand separately provided using the cross-carrier scheduling for thescheduling of the PDSCH to be mapped to the NCT.

The configuration by the legacy carrier is not required as to which ofthe E-PDCCH and the cross-carrier scheduling is used. The UE recognizesthe scheduling method based on whether or not there is an uplink forlink in the system information of the NCT. Specifically, in the casewhere there is an uplink for link in the system information of the NCT,the UE recognizes that the E-PDCCH is used to notify the scheduling ofthe PDSCH to be mapped to an NCT. In the case where there is no uplinkfor link in the system information of the NCT, the UE recognizes thatthe cross-carrier scheduling is used to notify the scheduling of thePDSCH to be mapped to the NCT.

Unlike Non-Patent Document 19, the solution (1) does not need anexplicit configuration by the legacy carrier, eliminating the need forproviding new signaling. Therefore, the communication system can beprevented from becoming complicated.

(2) In the case where the carrier aggregation is performed orconfigured, the cross-carrier scheduling is used to notify thescheduling of the PDSCH to be mapped to an NCT. Specifically, in thecase where the scheduling legacy carrier is a PCell or the schedulinglegacy carrier is an SCell, the cross-carrier scheduling is used tonotify the scheduling of the PDSCH to be mapped to an NCT. In the casewhere the scheduling legacy carrier is not a PCell and the schedulinglegacy carrier is not an SCell, the E-PDCCH may be used to notify thescheduling of the PDSCH to be mapped to the NCT.

The cross-carrier scheduling has been traditionally disclosed, in whichthe scheduling of the PDSCH to be mapped to an SCell is notified the UEover the PDCCH of the PCell (see Chapter 11.1 of Non-Patent Document 1).Therefore, the scheduling of the PDSCH to be mapped to an SCell and thescheduling of the PDSCH to be mapped to an NCT can also be thecross-carrier scheduling, preventing the communication system frombecoming complicated.

The third modification of the second embodiment described above canachieve the effects similar to those of the second embodiment.

Fourth Modification of Second Embodiment

The problem to be solved in a fourth modification of the secondembodiment will be described. Cross-carrier scheduling has beentraditionally disclosed, in which the scheduling of the PDSCH to bemapped to an SCell is notified the UE over the PDCCH of the PCell (seeNon-Patent Document 2). Specifically, the starting OFDM symbol for thePDSCH of the SCell is specified using a “pdsch-Start” parameter includedin “CrossCarrierSchedulingConfig.”

The values of the parameters are “1,” “2,” “3,” and “4.” Theseparameters show the starting OFDM symbol for the PDSCH described inChapter 7.1.6.4 of TS 36.213 V10.6.0 (hereinafter, referred to as“Non-Patent Document 20”) by 3GPP. As shown in Table 6.7-1 of TS 36.211V10.5.0 (hereinafter, referred to as “Non-Patent Document 21”) by 3GPP,parameter values “1,” “2,” and “3” can be used for the downlinkbandwidth of the SCell exceeding 10 resource blocks. As shown in Table6.7-1 of Non-Patent Document 21, the parameter values “2,” “3,” and “4”can be used for the downlink bandwidth of the SCell not greater than 10resource blocks.

In other words, the parameter value “1” denotes the starting OFDM symbolfor the PDSCH, for the downlink bandwidth of the SCell exceeding 10resource blocks, when the number of OFDM symbols for PDCCH is “1.”

The parameter value “2” denotes the starting OFDM symbol for the PDSCH,for the downlink bandwidth of the SCell exceeding 10 resource blocks,when the number of OFDM symbols for PDCCH is “2.” Alternatively, theparameter value “2” denotes the starting OFDM symbol for the PDSCH, forthe downlink bandwidth of the SCell not greater than 10 resource blocks,when the number of OFDM symbols for PDCCH is “2.”

The parameter value “3” denotes the starting OFDM symbol for the PDSCH,for the downlink bandwidth of the SCell exceeding 10 resource blocks,when the number of OFDM symbols for PDCCH is “3.” Alternatively, theparameter value “3” denotes the starting OFDM symbol for the PDSCH, forthe downlink bandwidth of the SCell not greater than 10 resource blocks,when the number of OFDM symbols for PDCCH is “3.”

The parameter value “4” denotes the starting OFDM symbol for the PDSCH,for the downlink bandwidth of the SCell not greater than 10 resourceblocks, when the number of OFDM symbols for PDCCH is “4.”

3GPP is studying to reduce PDCCHs (see Non-Patent Document 15). Asdescribed above, however, in cross-carrier scheduling in which thescheduling of the PDSCH to be mapped to an SCell is notified the UE overthe PDCCH of the PCell, the number of starting OFDM symbols for thePDSCH cannot be specified in the case where the number of OFDM symbolsfor PDCCH is “0.”

Therefore, the following problem occurs; the scheduling of the PDSCH tobe mapped to an NCT is not enabled through signaling of thecross-carrier scheduling in which the scheduling of the PDSCH to bemapped to the SCell is notified the UE over the PDCCH of the PCell.

The solution in the fourth modification of the second embodiment will bedisclosed below. The parameter indicating the starting OFDM symbol forthe PDSCH in the case where the number of OFDM symbols of the PDCCH tobe scheduled is “0” is added. Alternatively, the parameter indicatingthe starting OFDM symbol for the PDSCH, for the downlink bandwidth to bescheduled exceeding 10 resource blocks or for the downlink bandwidth notgreater than 10 resource blocks, when the number of OFDM symbols of thePDCCH to be scheduled is “0” is added. As a specific example, “0” isadded to the parameter value. The value “0” may indicate the startingOFDM symbol for the PDSCH when the number of OFDM symbols for PDCCH tobe scheduled is “0.”

The parameter values “0,” “1,” “2,” and “3” can be used for the downlinkbandwidth of the SCell exceeding 10 resource blocks, as shown in Table6.7-1 of Non-Patent Document 21. Alternatively, the parameter values“0,” “2,” “3,” and “4” can be used for the downlink bandwidth of theSCell not greater than 10 resource blocks, as shown in Table 6.7-1 ofNon-Patent Document 21.

The fourth modification of the second embodiment can achieve thefollowing effects. The scheduling of the PDSCH to be mapped to an NCT isenabled through signaling of the cross-carrier scheduling in which thescheduling of the PDSCH to be mapped to the SCell is notified the UEover the PDCCH of the PCell. This prevents the communication system frombecoming complicated.

Third Embodiment

The problem to be solved in a third embodiment will be described. Anobject of the introduction of an NCT is to improve support for HetNet(see Non-Patent Document 11). An improved support for HetNet isinter-cell interference coordination (ICIC). Examples of the cause foran occurrence of inter-cell interference include the PDCCH and SS beingdownlink control signals from the base station in the traditionaltechniques. Therefore, reducing the PDCCHs being the downlink controlsignals in the NCT is proposed as a concrete measure taken for theimproved support for HetNet (see Non-Patent Document 15). However,Non-Patent Documents 11 and 15 do not disclose, for example, the methodof causing base stations to cooperate with each other.

It is proposed that a load information message is transferred betweenbase stations as the method of causing base stations to cooperate witheach other in inter-cell interference coordination (see Non-PatentDocument 16).

In the case where the load information message contains a “ULInterference Overload Indication” parameter, the notification cell showsthat it suffers from interference for every resource block and everyphysical resource block (PRB). The base station that has received thisparameter takes that information into consideration. The base stationthat has received the “UL Interference Overload Indication” parametermay take that information into consideration in scheduling.

In the case where the load information message contains a “UL HighInterference Indication” parameter, it is indicated that highinterference occurs per PRB of the cell that notifies the parameter(hereinafter, also referred to as a “notification cell”). The basestation that has received the parameter (hereinafter, also referred toas a “reception base station”) should avoid scheduling the UE beingserved by the reception base station to a related PRB.

In the case where the load information message contains an “InvokeIndication IE” parameter, the base station that notifies the parameter(hereinafter, also referred to as a “notification base station”) showsto what information the reception base station wants to be responded.The reception base station may take into consideration the request madeby the “Invoke Indication IE” parameter.

In the case where “ABS Information” is set in “Invoke Indication IE,”the notification base station shows, to the reception base station, arequest for an almost blank subframe (ABS) configuration of thereception base station.

As described above, the present method of causing base stations tocooperate with each other for inter-cell interference coordination doesnot take an NCT into consideration. This embodiment therefore has anobject to disclose the improved support for HetNet in which basestations cooperate with each other in consideration of an NCT.

In the third embodiment including a modification, an NCT is taken as acell for convenience. This makes it easy to use the parameter systemregarding the cell (served cell) configured by the base station, whichis used in the existing X2 signaling between base stations.

The following two (1) and (2) will be disclosed as the solution in thethird embodiment.

(1) The eNB1 with high downlink interference will not notify a neighborcell of a request operation. The message indicating high downlinkinterference is newly provided. The cell identity of the cell with highdownlink interference, which is configured by the eNB1, may be notifiedtogether. The cell with high downlink interference corresponds to ahigh-interference cell.

A “parameter indicating high downlink interference” may be added to aload information message. The parameter may be added as a new message inaddition to the load information message. This prevents thecommunication system from becoming complicated because no new messageneeds to be added.

The following four (1-1) to (1-4) will be disclosed as the operation ofthe base station (hereinafter, referred to as “eNB2”) that has receivedthe message indicating high downlink interference.

(1-1) The PDSCH is scheduled and mapped to a cell having a carrierfrequency different from the carrier frequency of the cell with highdownlink interference configured by the eNB1. This reduces the PDSCHs ofthe cell having the same frequency carrier as that of the cell with highdownlink interference of the eNB2, reducing interference.

(1-2) In the case where the eNB2 configures an NCT, the eNB2 maypreferentially schedule and map a PDSCH to the NCT. The eNB2 mayschedule and map a PDSCH to the NCT. In the case where the eNB2configures an NCT, the eNB2 may schedule and map the PDSCH to the NCThaving a carrier frequency different from the carrier frequency of thecell with high downlink interference configured by the eNB1. Thisreduces the PDSCHs of the cell having the same frequency carrier as thatof the cell with high downlink interference of the eNB2, preventinginterference.

(1-3) In addition to (1-2) above, the eNB2 may avoid cross-carrierscheduling of the NCT from the legacy carrier having the same frequencycarrier as that of the cell with high downlink interference. Thisreduces the PDSCHs and PDCCHs of the cell having the same frequencycarrier as that of the cell with high downlink interference of the eNB2,preventing interference.

(1-2) and (1-3) above may be operated independently, with similareffects.

(1-4) The eNB2 changes the legacy carrier having the same frequencycarrier as that of the cell with high downlink interference to an NCT.The eNB2 changes the legacy carrier having the same frequency carrier asthat of the cell with high downlink interference to an NCT and does nottransmit downlink control signals such as PDCCH and SS.

The eNB2 may notify the eNB1 of a response indicating whether or not ithas responded to the request. The eNB2 may notify the eNB1 of theperformed operation together.

(2) The eNB1 with high downlink interference notifies neighbor cells ofthe request operation. The request operation may differ between the casewhere the neighbor cell includes an NCT and the neighbor cell includesno NCT. Alternatively, the request operation may differ between the casewhere the neighbor cell includes a configured NCT and the case where theneighbor cell includes no configured NCT. Still alternatively, therequest operation may differ between the case where the neighbor cellincludes an activated NCT and the case where the neighbor cell includesno activated NCT.

Specific examples of the method of judging whether or not neighbor cellincludes an NCT include the following methods. The notification of theinformation on whether or not the own base station configures an NCT isnewly provided between base stations. Alternatively, the notification ofthe information on whether or not the own base station configures an NCTfor any UE may be newly provided. Still alternatively, the notificationof the information on whether or not the own base station includes an“activated” NCT may be newly provided. The configuration of an NCT orthe system information of an NCT may be notified together with theabove-mentioned notification. A specific example of the configuration ofan NCT will be described below. The notification of whether or not anNCT is configured for the existing X2 signaling may be added to theabove-mentioned notification. This eliminates the need for adding newsignaling to configure an NCT, preventing the communication system frombecoming complicated.

Specific examples of the existing X2 signaling include “X2 SETUPRequest,” “X2 SETUP RESPONSE,” and “ENB CONFIGURATION UPDATE” (forexample, see Chapter 9.2.8 of Non-Patent Document 16). The informationon an NCT may be added to “Served Cell Information” during signaling andthe information on whether the carrier is a legacy carrier or an NCT maybe added.

The inquiry of whether or not the base station configures an NCT,whether or not there is an NCT configured for any UE, or whether or notthere is an activated NCT may be newly provided. The base station thathas received the inquiry responds to this inquiry.

The following twelve (1) to (12) will be disclosed as specific examplesof the configuration of an NCT notified between base stations. Thedetailed description of a parameter is similar to that of the secondmodification of the first embodiment, which will not be given here.

(1) A parameter for differentiating between a legacy carrier and an NCT.Notifying this parameter between base stations allows for the judgmenton whether or not a neighbor cell configures an NCT. This enablesimproved support for HetNet in which base stations cooperate with eachother in consideration of an NCT. Besides, inter-cell interferencecoordination in which base stations cooperate with each other inconsideration of an NCT is enabled.

(2) A cell identity of an NCT.

(3) Information on with which carrier an NCT is associated, for example,the information on an associated legacy carrier. This parameter can benotified between base stations not only to provide improved support forHetNet in which base stations cooperate with each other in considerationof an NCT but alto to achieve the following effect. The measurementconfiguration or the like can be appropriately determined for a UE beingserved by the cell configured by the own base station.

(4) A carrier frequency of an NCT. This parameter can be notifiedbetween base stations not only to provide improved support for HetNet inwhich base stations cooperate with each other in consideration of an NCTbut also to archive the following effect. The measurement configurationor the like can be appropriately determined for a UE being served by thecell configured by the own base station.

(5) A bandwidth of an NCT.

(6) A method of transmitting reference signals (RS s). This parametercan be notified between base stations not only to provide improvedsupport for HetNet in which base stations cooperate with each other inconsideration of an NCT but also to achieve the following effects. Themeasurement configuration or the like can be appropriately determinedfor a UE being served by the cell configured by the own base station. Asa specific example, the transmission number of RS s of a measurementtarget NCT, the bandwidth at which a CRS is transmitted, or the like canbe notified the UE as the measurement configuration. For example, how totake an average can be notified as the measurement configuration inaccordance with the number of CRS s of a measurement target for the UE.

(7) An index of an NCT.

(8) Location information on the place in which an NCT point isinstalled. This parameter can be notified between base stations not onlyto provide improved support for HetNet in which base stations cooperatewith each other in consideration of an NCT but also to achieve thefollowing effects. The location information can be used to, for example,determine a handover destination. As a specific example, the cell thatcan use an NCT closer to the UE can be determined as a target cell. Forexample, an associated legacy carrier (parameter (3) above) of an NCTcloser to the UE can be determined as a target cell. Using an NCT closerto the UE reduces the transmission power of uplink data of the UE,reducing the power consumption of the UE.

(9) Information indicating synchronization or non-synchronization. Thisparameter can be notified between base stations not only to provideimproved support for HetNet in which base stations cooperate with eachother in consideration of an NCT but also to archive the followingeffects. The information can be used to, for example, determine ahandover destination. For example, if the UE is allowed not to support anon-synchronized NCT as the capability of the UE, the cell that can usethe synchronized NCT as the target cell for the UE can be determined asa target cell. For example, the associated legacy carrier (parameter (3)above) for a synchronized NCT can be determined as a target cell.

(10) Information on uplink of an NCT. This parameter can be notifiedbetween base stations not only to provide improved support for HetNet inwhich base stations cooperate with each other in consideration of an NCTbut also to achieve the following effect. The information can be usedto, for example, determine a handover destination.

(11) Information on the TAG to which an NCT belongs. This parameter canbe notified between base stations not only to provide improved supportfor HetNet in which base stations cooperate with each other inconsideration of an NCT but also to archive the following effect. Theinformation can be used to, for example, determine a handoverdestination.

(12) Combination of (1) to (11) above.

The following five (2-1) to (2-5) will be disclosed as specific examplesof the operation in which the eNB1 with high downlink interferencenotifies a neighbor cell.

(2-1) In the case where the eNB2 has no NCT (in the case where the eNB2does not configure an NCT), the eNB1 with high downlink interferencerequests to schedule and map the PDSCH to a cell of other carrierfrequency. The “request to schedule and map the PDSCH to the cell ofother carrier frequency” may be added to the “Invoke Indication IE”parameter of the load information message. No new signaling needs to beadded, preventing the communication system from becoming complicated.

(2-2) In the case where the eNB2 has no configured NCT, the eNB1 withhigh downlink interference requests to configure an NCT. Alternatively,in the case where the eNB2 includes no activated NCT, the eNB1 with highdownlink interference may request to activate an NCT. The “request toconfigure an NCT” or the “request to activate an NCT” may be added tothe “Invoke Indication IE” parameter of a load information message. Thiseliminates the need for adding new signaling, preventing thecommunication system from becoming complicated.

(2-3) In addition to the specific example (2-2) above or in the casewhere the eNB2 includes an NCT, the eNB1 with high downlink interferencerequests to schedule and map the PDSCH to an NCT. The “request toschedule and map the PDSCH to an NCT” may be added to the “InvokeIndication IE” parameter of the load information message. Thiseliminates the need for adding new signaling, preventing thecommunication system from becoming complicated.

(2-4) In addition to the specific example (2-3) above, in the case wherethe eNB2 includes an NCT, the eNB1 with high downlink interference mayrequest not to perform cross-carrier scheduling of the NCT from thelegacy carrier having the same frequency carrier as that of the cellwith high downlink interference. The “request not to performcross-carrier scheduling of the NCT from the legacy carrier having thesame frequency carrier as that of the cell with high downlinkinterference” may be added to the “Invoke Indication IE” parameter of aload information message. This eliminates the need for adding newsignaling, preventing the communication system from becomingcomplicated.

The specific example (2-2), the specific example (2-3), and the specificexample (2-4) above may be independently operated, with similar effects.

(2-5) The eNB1 with high downlink interference requests the eNB2 tochange the carrier having the same frequency carrier as that of the cellwith high downlink interference to an NCT. The eNB1 requests to changethe carrier having the same frequency carrier as that of the cell withdownlink interference to an NCT and not to transmit downlink controlsignals such as PDCCH and SS. This specific example can be used in boththe case where the eNB2 includes an NCT and the case where the eNB2includes no NCT. The cell identity of the cell with high downlinkinterference configured by the eNB1 may be notified together.

The eNB2 that has received the “request to schedule and map the PDSCH tothe cell of other carrier frequency” schedules and maps the PDSCH to thecell of a carrier frequency different from the carrier frequency of thecell with high downlink interference configured by the eNB1. Thisreduces the PDSCHs of the cell having the same frequency carrier as thatof the cell with high downlink interference of the eNB2, preventinginterference.

The eNB2 that has received the “request to schedule and map the PDSCH tothe NCT” schedules and maps the PDSCH to the NCT. The eNB2 schedules andmaps the PDSCH to the NCT having a carrier frequency different from thecarrier frequency of the cell with high downlink interference configuredby the eNB1. This reduces PDSCHs of the cell having the same frequencycarrier as that of the cell with high downlink interference of the eNB2,preventing interference.

The eNB2 that has received the “request not to perform cross-carrierscheduling of the NCT from the legacy carrier having the same frequencycarrier as that of the cell with high downlink interference” may avoidcross-carrier scheduling of the NCT from the legacy carrier having thesame frequency carrier as that of the cell with high downlinkinterference. This reduces PDSCHs and PDCCHs of the cell having the samefrequency carrier as that of the cell with high downlink interference ofthe eNB2, preventing interference.

The eNB2 may notify the eNB1 of a response as to whether or not the eNB2has responded to the request. The configuration (such as systeminformation) of the configured NCT or the configuration (such as systeminformation) of the activated NCT may be notified. The existing X2signaling may be used in this notification. This eliminates the need foradding new signaling, preventing the communication system from becomingcomplicated. Specific examples of the existing X2 signaling include “ENBCONFIGURATION UPDATE” (see Non-Patent Document 16).

FIG. 31 shows an example sequence of the communication system in thesolution (1) according to the third embodiment of the present invention.

In Step ST3001, the eNB1 whose downlink interference has become highernotifies the eNB2 being a neighbor cell that the downlink interferencehas become higher. As a result, the eNB1 issues a counter-interferencerequest to request a measure against interference to the eNB2.

In Step ST3002, the eNB2 that has been notified that the downlinkinterference has become higher from the eNB1 in Step ST3001 judgeswhether or not to respond to the counter-interference request. In thisjudgment, the eNB2 may make determination in consideration of, forexample, the status of the cell configured by the eNB2, the resourcestatus, and the processing load. The eNB2 moves to Step ST3003 whenjudging to respond to the counter-interference request. The eNB2 movesto Step ST3008 when judging that it does not to respond to thecounter-interference request or it cannot respond to thecounter-interference request.

In Step ST3003, the eNB2 judges whether or not the own base stationconfigures an NCT. The eNB2 moves to Step ST3004 when judging that theown base station configures an NCT. The eNB2 moves to Step ST3006 whenjudging that the own base station does not configure an NCT.

In Step ST3004, the eNB2 schedules and maps the PDSCH to the NCT that isconfigured by the eNB1 and has a carrier frequency different from thecarrier frequency of the cell with high downlink interference.

In Step ST3005, the eNB2 prohibits cross-carrier scheduling of the NCTfrom the legacy carrier having the same frequency carrier as that of thecell with high downlink interference.

In Step ST3006, the eNB2 schedules and maps the PDSCH to the cell thatis configured by the eNB1 and has a carrier frequency different from thecarrier frequency of the cell with high downlink interference.

In Step ST3007, the eNB2 transmits, to the eNB1, “Ack” indicating thatit has responded to the counter-interference request of the eNB1 and hastaken a measure.

In Step ST3008, the eNB2 transmits, to the eNB1, “Nack” indicating thatit has not responded to the counter-interference request of the eNB1 andhas taken no measure.

FIG. 32 shows an example sequence of the communication system in thesolution (2) of the third embodiment of the present invention. Thesequence shown in FIG. 32 is similar to the sequence shown in FIG. 31,and thus, the same steps will be denoted by the same step numbers andcommon description will be omitted.

In Step ST3101, the eNB1 notifies the eNB2 of the information on whetheror not the eNB1 configures an NCT using an X2 setup request (X2 SETUPRequest).

In Step ST3102, the eNB2 notifies the eNB1 of the information on whetheror not the eNB2 configures an NCT using an X2 setup response (X2 SETUPResponse).

In Step ST3103, the eNB1 judges whether or not the downlink interferenceof the own base station is high. Whether or not the downlinkinterference is high may be judged per cell configured by the eNB1. TheeNB1 moves to Step ST3104 in the case when judging that the downlinkinterference is high. The eNB1 repeats the judgment of Step ST3103 whenjudging that the downlink interference is not high.

In Step ST3104, the eNB1 judges whether or not the eNB2 being a neighborcell configures an NCT. The eNB1 may use the information received inStep ST3102 in this judgment. The eNB1 moves to Step ST3105 when judgingthat the neighbor cell does not configure an NCT. The eNB1 moves to StepST3106 when judging that the neighbor cell configures an NCT.

In Step ST3105, the eNB1 notifies the eNB2 of the “request to scheduleand map the PDSCH to the cell of other carrier frequency.”

In Step ST3106, the eNB1 notifies the eNB2 of the “request to scheduleand map the PDSCH to an NCT.” As a result of this notification, the“request not to perform cross-carrier scheduling the NCT from the legacycarrier having the same frequency carrier as that of the cell with highdownlink interference” may also be notified.

In Step ST3107, the eNB2 judges whether or not to have received the“request to schedule and map the PDSCH to the cell of other carrierfrequency” or the “request to schedule and map the PDSCH to the NCT”from the eNB1. The eNB2 moves to Step ST3006 when judging to havereceived the “request to schedule and map the PDSCH to the cell of othercarrier frequency.” The eNB2 moves to Step ST3004 when judging to havereceived the “request to schedule and map the PDSCH to an NCT.”

The third embodiment described above can achieve the following effects.The improved support for HetNet in which base stations cooperate witheach other in consideration of an NCT can be enabled. In addition,inter-cell interference coordination in which base stations cooperatewith each other in consideration of an NCT can be enabled.

First Modification of Third Embodiment

The problem to be solved in the first modification of the thirdembodiment will be described. The purposes of introducing an NCT includeimproved support for HetNet and improved frequency use efficiency (seeNon-Patent Document 11). 3GPP has not discussed how to satisfy both thetwo purposes of introducing an NCT. The first modification of the thirdembodiment therefore aims to disclose the method of satisfying both theimproved support for HetNet and the improved frequency use efficiency,which are the purposes of introducing an NCT.

The solution in the first modification of third embodiment will bedisclosed below. The information on the number of OFDM symbols for PDCCHis notified between base stations. The information on the number of OFDMsymbols for PDCCH per cell configured by the base station is notified.The PDSCH is not mapped in the case where the PDCCH of a neighbor cellis mapped, whereas the PDSCH is mapped in the case where the PDCCH of aneighbor cell is not mapped.

Reducing PDCCHs is studied particularly as to the NCT, as describedabove. Thus, the method of using the resources of the first to thefourth symbols in which the PDCCH is mapped in the legacy carrier hasnot been determined. In the case where the PDCCH of a neighbor cell ismapped, the effect of reducing interference with the neighbor cell canbe achieved by avoiding mapping the PDSCH. In the case where the PDCCHof a neighbor cell is not mapped, the following effect is achieved bymapping the PDSCH; resources can be used effectively and frequency useefficiency can be improved.

Hereinafter, the base station with high downlink interference isreferred to as “eNB1.” A neighbor cell for the eNB1 is referred to as“eNB2.” For example, in the case where the numbers of OFDM symbols forPDCCH from the neighbor base stations including the eNB1 are “1” and“2,” the eNB2 does not schedule and map the PDSCH to the first andsecond symbols and starts scheduling and mapping the PDSCH starting fromthe third symbol.

A specific example of the notification of the information on the numberof OFDM symbols for PDCCH between base stations will now be described.

The notification of the information on the number of OFDM symbols forPDCCH is newly provided between base stations. As a specific example,the numbers of OFDM symbols for PDCCH “0,” “1,” “2,” and “3” for thedownlink bandwidth exceeding 10 resource blocks will be notified. Inaddition, the numbers of OFDM symbols for PDCCH “0,” “2,” “3,” and “4”for the downlink bandwidth not greater than 10 resource blocks arenotified. The system information of an NCT may be notified together inthis notification. A specific example of the system information of anNCT is similar to that of the second modification of the firstembodiment, which will not be given here.

This notification may be performed by adding the number of OFDM symbolsfor PDCCH to the existing X2 signaling. In this case, it is notnecessary to add new signaling for the number of OFDM symbols for PDCCH,preventing the communication system from becoming complicated. Specificexamples of the existing X2 signaling include “X2 SETUP Request,” “X2SETUP RESPONSE,” and “ENB CONFIGURATION UPDATE” (for example, seeChapter 9.2.8 of Non-Patent Document 16). The number of OFDM symbols forPDCCH may be added to “Served Cell Information” during signaling.

The following three (1) to (3) will be disclosed as the specific methodof operating the eNB1 and the eNB2.

(1) The cell configured by the eNB2 that has received the number of OFDMsymbols for PDCCH of the eNB1 prohibits scheduling and mapping of thePDSCH to the OFDM symbols. The cell of the same carrier frequency mayprohibit scheduling and mapping of the PDSCH to the OFDM symbols.

The NCT configured by the eNB2 that has received the number of OFDMsymbols for PDCCH of the eNB1 prohibits scheduling and mapping of thePDSCH to the OFDM symbols. The NCT of the same carrier frequency mayprohibit scheduling and mapping of the PDSCH to the OFDM symbols.

The eNB2 receives the number of OFDM symbols for PDCCH from neighborbase stations including the eNB1 and allows scheduling and mapping ofthe PDSCH to the OFDM symbol being not used in the PDCCH.

The method (1) requires the eNB1 to notify the eNB2 of only the numberof OFDM symbols for PDCCH, preventing the communication system frombecoming complicated.

(2) In the case where the load information message contains thenotification of the “parameter indicating high downlink interference”disclosed in the third embodiment, the cell configured by the eNB2 thathas received the number of OFDM symbols for PDCCH of the eNB1 prohibitsscheduling and mapping of the PDSCH to the OFDM symbols. The cell of thesame carrier frequency may prohibit scheduling and mapping of the PDSCHto the OFDM symbols.

In the case where the load information message contains the notificationof the “parameter indicating high downlink interference” disclosed inthe third embodiment, the NCT configured by the eNB2 that has receivedthe number of OFDM symbols for PDCCH of the eNB1 prohibits schedulingand mapping of the PDSCH to the OFDM symbols. The NCT of the samecarrier frequency may prohibit scheduling and mapping of the PDSCH tothe OFDM symbols.

Also in the case where the load information message contains thenotification of the “parameter indicating high downlink interference”disclosed in the third embodiment, the eNB2 receives the number of OFDMsymbols for PDCCH from neighbor base stations including the eNB1, andschedules and maps the PDSCH to the OFDM symbol being not used in thePDCCH.

In the case where the “parameter indicating high downlink interference”disclosed in the third embodiment is not notified, the eNB2 schedulesand maps the PDSCH to the OFDM symbol that is not used for the PDCCH inthe own cell.

In the case where the downlink interference of a neighbor cell is nothigh, the PDSCH can be scheduled and mapped to the OFDM symbol that isnot used for the PDCCH in the own cell. This allows the resources to beused further effectively and improves frequency use efficiency comparedwith the method (1).

(3) The eNB1 with high downlink interference requests the eNB2 not toschedule and map the PDSCH to the area to which the own PDCCH is mapped.In the case where the eNB2 includes an NCT, the eNB1 with high downlinkinterference may request the eNB2 not to schedule and map the PDSCH tothe area to which the own PDCCH is mapped. The “request not to scheduleand map the PDSCH to the area to which the own PDCCH is mapped” may beadded to the “Invoke Indication IE” parameter of the load informationmessage. It is not necessary to add new signaling, preventing thecommunication system from becoming complicated. The eNB2 may notify theeNB1 of the response to whether or not the eNB2 has responded to therequest.

The methods (2) and (3) above can be used in combination.

FIG. 33 shows an example sequence in the case where the specific method(1) of operating the eNB1 and the eNB2 is used in the communicationsystem according to the first modification of the third embodiment ofthe present invention.

In Step ST3201, the eNB1 notifies the eNB2, using an X2 SETUP Request,of the information on the number of OFDM symbols for PDCCH of the eNB1.

In Step ST3202, the eNB2 notifies the eNB1, using an X2 SETUP Response,of the information on the number of OFDM symbols for PDCCH of the eNB2.

In Step ST3203, the eNB2 prohibits scheduling and mapping of the PDSCHto the OFDM symbols for PDCCH of the neighbor cells including the eNB1.

In Step ST3204, the eNB2 permits scheduling and mapping of the PDSCH tothe symbols excluding the OFDM symbols for PDCCH of the neighbor cellsincluding the eNB1.

The eNB1 performs the processes similar to those of Steps ST3203 andST3204, which is not shown in FIG. 33.

FIG. 34 shows an example sequence in the case where the specific methods(2) and (3) of operating the eNB1 and the eNB2 are used in combinationin the communication system according to the first modification of thethird embodiment of the present invention. The sequence shown in FIG. 34is similar to the sequences shown in FIGS. 31 and 33, and thus, the samesteps will be denoted by the same step numbers and common descriptionwill be omitted.

In Step ST3301, the eNB1 whose downlink interference has become highernotifies the eNB2 being a neighbor cell that its downlink interferencehas become higher. Upon this, the eNB1 issues a counter-interferencerequest to the eNB2. In this case, the eNB1 may also notify “the requestnot to schedule and map the PDSCH to the area to which the own PDCCH ismapped.”

In Step ST3002, the eNB2 that has been notified from the eNB1 that thedownlink interference of the eNB1 has become higher in Step ST3301judges whether or not to respond to the counter-interference request.This judgment may be made in consideration of, for example, the statusof the cell configured by the eNB2, the resource status, and theprocessing load. When judging to respond to the counter-interferencerequest, the eNB1 moves to Step ST3203. When judging that it will not orcannot respond to the counter-interference request, the eNB1 moves toStep ST3008.

The first modification of the third embodiment can achieve the followingeffects in addition to the effects of the third embodiment. Frequencyuse efficiency can be improved by performing inter-cell interferencecoordination in the case where the neighbor cell suffers frominterference or by effectively using resources in the case where theneighbor cell is free from interference. This satisfies improved supportfor HetNet and improved frequency use efficiency, which are the objectsof introducing an NCT.

Fourth Embodiment

The problem to be solved in a fourth embodiment will be described.

An object of introducing an NCT is to reduce the power consumption of asystem (see Non-Patent Document 11). It is proposed to reduce CRS s inan NCT, as a specific measure for energy saving of a communicationsystem (see Non-Patent Document 15). Non-Patent Documents 11 and 15however do not disclose, for example, the method of causing basestations to cooperate with each other for energy saving of acommunication system.

The method disclosed below is an example of the method of causing basestations to cooperate with each other for energy saving of a system. The“deactivation indication” parameter is exchanged between base stationsin switching off a cell. This indicator is notified in a base stationupdate message (ENB CONFIGURATION UPDATE).

The base station notifies a neighbor base station of a cell activationrequest message (CELL Activation Request) that requests to switch on thecell.

The method of causing base stations to cooperate with each other forenergy saving of a communication system, described above, does not takean NCT into consideration. This embodiment thus aims to disclose thesupport for energy saving of a communication system in which basestations cooperate with each other in consideration of an NCT.

The fourth embodiment including modifications take an NCT as a cell forconvenience. This allows for easy use of the parameter system regardingthe cell (served cell) configured by the base station, which is used inthe existing X2 signaling between base stations.

The solution in the fourth embodiment will be disclosed below. Whetherthe cell being a switching off target is a legacy carrier or an NCT isnotified between base stations. The information on whether or not thecell is an NCT may be notified. Description will now be given of thecase where a cell 1 configured by the eNB1 is switched off and the eNB2is notified.

In the case where, for example, the resources for the cell configured bythe eNB2 become insufficient or the processing load becomes high, theeNB2 considers switching on the cell of a neighbor base station.

In the consideration, the eNB2 judges whether it is suitable to switchon a legacy carrier or to switch on an NCT. This judgment may be madebased on, for example, the policy for energy saving of a communicationsystem of an operator. This policy may be notified the eNB from anoperation administration and maintenance (OAM).

The eNB2 notifies that it will request to switch on an NCT or a legacycarrier in accordance with the judgment results.

The following two (1) and (2) will be disclosed as specific examples ofthe method of notifying whether the cell being a switching off target isa legacy carrier or an NCT between base stations.

(1) Notification of the information on whether or not an NCT isconfigured is newly provided between base stations. The configuration ofan NCT or the system information of an NCT may be notified together inthe above-mentioned notification. A specific example of theconfiguration of an NCT is similar to that of the third embodiment,which will not be described here. This notification may be made byadding the notification of whether or not an NCT is configured for theexisting X2 signaling. It is not necessary to add new signaling for theconfiguration of an NCT, preventing the communication system frombecoming complicated.

Specific examples of the existing X2 signaling include “X2 SETUPRequest,” “X2 SETUP RESPONSE,” and “ENB CONFIGURATION UPDATE” (forexample, see Chapter 9.2.8 of Non-Patent Document 16). The informationon an NCT may be added to “Served Cell Information” during thesignaling, thereby adding the information on whether the cell is alegacy carrier or an NCT. This allows the eNB2 to judge, for every cellconfigured by the eNB1, whether the cell is a legacy carrier or an NCT.

In switching off the cell configured by itself, the eNB1 notifies theeNB2 being a neighbor cell of switching off in a “Deactivationindication” parameter that is mapped to the “Served Cell Modify”parameter of “ENB CONFIGURATION UPDATE”, as in the traditionaltechnique.

The eNB2 can judge whether the cell that has been switched off is alegacy carrier or an NCT based on the information on whether or not thecell configures an NCT notified from the eNB1.

(2) The information on whether the cell being a switching off target isa legacy carrier or an NCT is newly provided to be notified, whenswitch-off is notified. In switching off the cell that is configured byitself, the eNB1 notifies the eNB2 being a neighbor cell of theswitch-off in a “Deactivation indication” parameter to be mapped to the“Served Cell Modify” parameter of “ENB CONFIGURATION UPDATE.” In thiscase, the information on whether the cell is a legacy carrier or an NCTis added. The information on whether or not the cell is an NCT may beadded.

Signaling indicating simultaneous switching off of the NCTs among thecells configured by the eNB1 may be newly provided. In notifying thesimultaneous switching off of the NCTs, “ENB CONFIGURATION UPDATE” to benotified by means of an X2 interface being the existing signaling may beused.

The following two (1) and (2) will be disclosed as specific examples ofthe method of requesting to switch on an NCT or a legacy carrier betweenbase stations.

(1) The information on whether or not an NCT is configured is newlyprovided between base stations. The system information of an NCT may benotified together in the above-mentioned notification. A specificexample is similar to the description disclosed in the method (1) ofnotifying whether the cell being a switching off target is a legacycarrier or an NCT between base stations, which will not be describedhere.

The eNB2 can judge, for every cell configured by the eNB1, whether thecell is a legacy carrier or an NCT. Thus, as in the traditionaltechnique, switching on of a relevant cell is requested in the “CELLActivation Request” message in accordance with the judgment result onwhether or not it is suitable to switch on a legacy carrier or to switchon an NCT.

(2) The information indicating the request to switch on a legacy carrieror to switch on an NCT is newly provided and notified in thenotification that the cell is switched on. This notification may use“CELL Activation Request” that is notified by means of an X2 interfacebeing the existing signaling.

The eNB1 may notify the eNB2 of a response as to whether or not the eNB1has responded to the request. For example, in the case where the eNB2notifies the eNB1 of the information indicating the request to switch onan NCT, the eNB1 notifies that it will not respond to the request if,for example, the eNB1 does not configure an NCT or there is no NCT beinga switching off target. In the case where the eNB2 notifies the eNB1 ofthe information indicating the request to switch on an NCT, the eNB1notifies that it has responded to the request if, for example, there isan NCT being a switching off target.

Alternatively, signaling notifying that NCTs are switched onsimultaneously may be newly provided. “CELL Activation Request” to benotified by means of an X2 interface being the existing signaling may beused to notify that NCTs are switched on simultaneously.

The method of notifying that the cell being a switching off target is alegacy carrier or an NCT between base stations (hereinafter, alsoreferred to as a “notification method”) and the method of requesting toswitch on an NCT or a legacy carrier between base stations (hereinafter,also referred to as a “request method”) may be appropriately combinedtogether. However, the specific example (1) of the notification methodand the specific example (1) of the request method are similar to eachother in that a notification of the information on whether or not an NCTis configured between base stations is newly provided, and accordingly,these examples are highly compatible with each other. The specificexample (2) of the notification method and the specific example (2) ofthe request method are similar to each other in that a notification ofthe information on whether or not an NCT is configured between basestations is not newly provided, and accordingly, these examples arehighly compatible with each other as a combination.

FIG. 35 shows an example sequence in the case where the specific example(1) of the notification method and the specific example (1) of therequest method are used in combination in the communication systemaccording to the fourth embodiment of the present invention. Thesequence shown in FIG. 35 is similar to the sequence shown in FIG. 32,and thus, the same steps will be denoted by the same step numbers andcommon description will be omitted.

In Step ST3101, the eNB1 notifies the eNB2 of the information on whetheror not the eNB1 configures an NCT in an X2 SETUP Request. For example,the eNB1 notifies that it configures a cell 1, a cell 2, and a cell 3and that the cell 1 is an NCT and the cells 2 and 3 are legacy carriers.

In Step ST3102, the eNB2 notifies the eNB1 of the information on whetheror not the eNB2 configures an NCT in an X2 SETUP Response.

In Step ST3401, the eNB1 notifies switching off the NCT, for example,switching off the cell 1.

In Step ST3402, the eNB2 recognizes that the cell 1 being an NCTconfigured by the eNB1 has been switched off using the informationreceived in Step ST3101 and the information received in Step ST3401.

In Step ST3403, the eNB2 judges whether or not an event that requests aneighbor cell to be switched on has occurred. As a specific example, theeNB2 judges whether or not the resources thereof have becomeinsufficient. When judging that the resources have become insufficient,the eNB2 moves to Step ST3404. When judging that the resources have notbecome insufficient, the eNB2 repeats the judgment of Step ST3403.

In Step ST3404, the eNB2 check the policy on energy saving (ES) of theoperator system. This policy is notified the eNB2 from an OAM or thelike. For example, it is set in the ES-related operator policy that anNCT is preferentially switched on.

In Step ST3405, the eNB2 judges whether or not there is an NCT beingswitched off in its neighborhood. The eNB2 moves to Step ST3406 whenjudging that there is such an NCT or moves to Step ST3408 when judgingthere is no such an NCT.

In Step ST3406, the eNB2 selects an NCT to be switched on from the NCTsbeing switched off in its neighborhood. Also in this case, the eNB2 maymake judgment based on the ES-related operator policy. For example, theeNB2 selects to switch on the cell 1 being an NCT configured by theeNB1.

In Step ST3407, the eNB2 instructs the eNB1 to switch on an NCT, forexample, switch on the cell 1.

In Step ST3408, the eNB2 selects a legacy carrier to be switched on fromthe legacy carriers being switched off in its neighborhood. Also in thiscase, the eNB2 may make judgment based on the ES-related operatorpolicy.

In Step ST3409, the eNB2 instructs the base station configuring thelegacy carrier selected in Step ST3408 to switch on the legacy carrier.

FIG. 36 shows an example sequence in the case where the specific example(2) of the notification method and the specific example (2) of therequest method are used in combination in the communication systemaccording to the fourth embodiment of the present invention. Thesequence shown in FIG. 36 is similar to the sequence shown in FIG. 32,and thus, the same steps will be denoted by the same step numbers andcommon description will be omitted.

In Step ST3501, the eNB1 notifies switching off the NCT, for example,switching off the cell 1. At that time, the eNB1 also notifies that thecell 1 is an NCT. That is, the eNB1 may notify switching off the cell 1being an NCT.

In Step ST3502, the eNB2 selects a base station to be notified ofswitch-on from the base stations including cells being switched off.Also in this case, the eNB2 may make judgment based on the ES-relatedoperator policy. For example, the eNB2 selects to switch on the eNB1.

In Step ST3503, the eNB2 instructs the eNB1 to switch on an NCT,specifically, to switch on the cell 1, among the cells configured by theeNB1.

The eNB1 that has received the instruction to switch on an NCT in StepST3503 switches on the cell 1 being an NCT and, in Step ST3504, notifiesthe eNB2 “Ack” indicating that the eNB1 has responded to the request.

In Step ST3505, the eNB2 judges whether or not to have received “Ack” asa response signal from the eNB1. The eNB2 ends the process when judgingto have received “Ack” or moves to Step ST3506 when judging to not havereceived “Ack.”

In Step ST3506, the eNB2 selects a base station to be notified ofswitch-on from the base stations including cells being switched off. Inthis case, the eNB2 may select a base station from the base stationsexcluding the eNB2.

The fourth embodiment described above can achieve the following effect.Energy saving of the system is enabled, in which base stations cooperatewith each other in consideration of an NCT.

First Modification of Fourth Embodiment

The first modification of the fourth embodiment will disclose anothersolution to the same problem as that of the fourth embodiment describedabove.

The solution in the first modification of the fourth embodiment will bedisclosed below. Description will be given of the case where the eNB2notifies the eNB1 of switch-on.

In the case where the resources of the cell configured by the eNB2become insufficient or the processing load becomes high, the eNB2considers switching on a cell of the neighbor base station.

In the consideration, the eNB2 judges whether it is suitable to switchon a legacy carrier or to switch on an NCT. This judgment may be madebased on the policy on energy saving of the communication system of theoperator. This policy may be notified the eNB from, for example, an OAM.

The eNB2 inquires about whether the cell being switched off, which isconfigured by the neighbor base station, is an NCT or a legacy carrierbeing switched off. The eNB2 may inquire about whether or not there isan NCT being switched off.

“Resource Status Request” (see Chapter 8.3.6.2 of Non-Patent Document16) notified by means of an X2 interface being the existing signalingmay be used in this inquiry. In this case, an indicator for inquiringabout “whether or not there is an NCT being switched off” may beprovided in the existing signaling. This eliminates the need for addingnew signaling, allowing for easy construction of a communication system.In addition, a communication system having excellent backwardcompatibility can be constructed.

“Resource Status Response” (see Chapter 8.3.6.2 of Non-Patent Document16) notified by means of an X2 interface being the existing signalingmay be used in the response to the inquiry. In this case, an indicatorindicating “whether or not there is an NCT being switched off” may beprovided in the existing signaling. This eliminates the need for addingnew signaling, allowing for easy construction of a communication system.In addition, a communication system having excellent backwardcompatibility can be constructed. In the notification of a response tothe inquiry, a cell identity may be notified together. This enables acell to be specified and switched on.

The eNB2 determines a base station that is notified of switch-on inaccordance with the policy on energy saving of a communication system ofthe operator and a response to the request. For example, in the policyon energy saving of a communication system of the operator, it is setthat an NCT is preferentially switched on. In that case, in a responseto the inquiry, the eNB2 instructs the base station that has respondedthat “there is an NCT being switched off” to switch on an NCT.

FIG. 37 shows an example sequence of the communication system in thesolution according to the first modification of the fourth embodiment ofthe present invention. The sequence shown in FIG. 37 is similar to thesequence shown in FIG. 35, and thus, the same steps will be denoted bythe same step numbers and common description will be omitted.

In Step ST3601, the eNB2 inquiries neighbor base stations including theeNB1 of whether or not there is an NCT being switched off.

In Step ST3602, the eNB1 notifies the eNB2 of a response to the inquiry.The eNB1 responds “that there is an NCT being switched off” or “thatthere is the cell 1 as an NCT being switched off.”

In Step ST3603, the eNB2 selects a base station to be notified ofswitch-on, in consideration of the ES-related operator policy and theresponse in Step ST3602. For example, the eNB2 selects the eNB1 as abase station to be notified of switch-on.

In Step ST3604, the eNB2 instructs the eNB1 to switch on the cell 1 thatis an NCT being switched off.

The first modification of the fourth embodiment above can achieveeffects similar to those of the fourth embodiment.

Second Modification of Fourth Embodiment

The second modification of the fourth embodiment will disclose anothersolution to the same problem as that of the fourth embodiment describedabove.

The solution in the second modification of the fourth embodiment will bedisclosed below. The base station may change the legacy carrier to anNCT for energy saving. This allows for energy saving of a communicationsystem through, for example, a reduction of CRSs.

If the resources become insufficient or the processing load becomeshigh, the base station may change an NCT to a legacy carrier. Thisincreases legacy carriers that can serve as a serving cell for a UEbeing served thereby, reducing the processing load of the base station.

When switch is made between a legacy carrier and an NCT, the informationon whether or not the relevant NCT configures an NCT of the own basestation, the configuration of an NCT, or the system information of anNCT will change. This information may be notified between base stations.A notification as to whether or not an NCT is configured for theexisting X2 signaling may be added to the above-mentioned notification.This eliminates the need for adding new signaling to configure an NCT,preventing a communication system from becoming complicated. Specificexamples of the existing X2 signaling include “ENB CONFIGURATION UPDATE”(for example, see Chapter 9.2.8 of Non-Patent Document 16).

The second modification of the fourth embodiment above can achieve thefollowing effect. Energy saving of a system that takes an NCT intoconsideration is enabled.

The embodiments and the modifications thereof are merely illustrationsof the present invention, and the embodiments and the modificationsthereof can be combined freely within the scope of the presentinvention. The elements of the embodiments and the modifications thereofcan be modified or omitted as required. Therefore, the communicationsystems of Release 11 and the following releases in which legacycarriers and NCTs coexist can be operated normally and efficiently.

While the invention has been shown and described in detail, theforegoing description is in all aspects illustrative and notrestrictive. It is therefore understood that numerous modifications andvariations can be devised without departing from the scope of theinvention.

DESCRIPTION OF REFERENCE NUMERALS

1401 NCT point; 1402, 1504 HARQ-MAC; 1403, 1505 PHY; 1501 existing cell;1502 RRC; 1503 MAC.

1: A mobile communication system in which a communication partner thatcommunicates with a user equipment is changed from a source base stationto a target base station, wherein a transmission configuration fortransmitting, to the user equipment, a reference signal to be referredby the user equipment is notified from the source base station to thetarget base station. 2: The mobile communication system according toclaim 1, wherein the transmission configuration is a configurationrelated to a frequency of performing transmission of the referencesignal. 3: The mobile communication system according to claim 2, whereinthe transmission configuration is a configuration in which the frequencyof performing transmission of the reference signal is less frequentlythan normal. 4: The mobile communication system according to claim 1,wherein the source base station notifies the target base station of thepresence or absence of the transmission configuration. 5: The mobilecommunication system according to claim 1, wherein the source basestation notifies the target base station of a frequency of a carrier fortransmitting the reference signal to the user equipment. 6: The mobilecommunication system according to claim 1, wherein the source basestation requests the target base station to change a partner thatcommunicates with the user equipment to the target base station. 7: Asource base station that is a communication partner of a user equipmentbefore a base station that communicates with the user equipment ischanged to a target base station, wherein the source base stationnotifies the target base station of a transmission configuration fortransmitting, to the user equipment, a reference signal to be referredby the user equipment. 8: A target base station that is a communicationpartner of a user equipment after a base station that communicates withthe user equipment is changed from a source base station, wherein thetarget base station receives, from the source base station, atransmission configuration for transmitting, to the user equipment, areference signal to be referred by the user equipment. 9: A userequipment that changes a communication partner form a source basestation to a target base station, wherein a transmission configurationfor transmitting, from the source base station, a reference signal to bereferred is notified from the source base station to the target basestation, and the user equipment receives and refers, according to thetransmission configuration, the reference signal transmitted from thetarget base station.